<?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>91</VOL>
    <NO>130</NO>
    <DATE>Thursday, July 9, 2026</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>
                Agriculture
                <PRTPAGE P="iii"/>
            </EAR>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Commodity Credit Corporation</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Forest Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Rural Business-Cooperative Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>42406-42407</PGS>
                    <FRDOCBP>2026-13813</FRDOCBP>
                      
                    <FRDOCBP>2026-13877</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>AIRFORCE</EAR>
            <HD>Air Force Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Board of Visitors of the U.S. Air Force Academy, </SJDOC>
                    <PGS>42427-42428</PGS>
                    <FRDOCBP>2026-13895</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Consumer Financial Protection</EAR>
            <HD>Bureau of Consumer Financial Protection</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Request for Information:</SJ>
                <SJDENT>
                    <SJDOC>Promoting Access to Mortgage Credit, </SJDOC>
                    <PGS>42382-42386</PGS>
                    <FRDOCBP>2026-13834</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fiscal</EAR>
            <HD>Bureau of the Fiscal Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Prompt Payment Interest Rate; Contract Disputes Act, </DOC>
                    <PGS>42594</PGS>
                    <FRDOCBP>2026-13903</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Medicare</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Secretarial Comments on the Consensus-Based Entity's (Battelle Memorial Institute) 2025 Activities:</SJ>
                <SJDENT>
                    <SJDOC>Report to Congress and the Secretary of the Department of Health and Human Services, </SJDOC>
                    <PGS>42451-42536</PGS>
                    <FRDOCBP>2026-13865</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Foreign-Trade Zones Board</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Oceanic and Atmospheric Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Commission Fine</EAR>
            <HD>Commission of Fine Arts</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Hearings, Meetings, Proceedings, etc., </DOC>
                    <PGS>42425</PGS>
                    <FRDOCBP>2026-13812</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Committee for Purchase</EAR>
            <HD>Committee for Purchase From People Who Are Blind or Severely Disabled</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Procurement List; Additions and Deletions, </DOC>
                    <PGS>42425-42427</PGS>
                    <FRDOCBP>2026-13839</FRDOCBP>
                      
                    <FRDOCBP>2026-13840</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commodity Credit</EAR>
            <HD>Commodity Credit Corporation</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Supplemental Disaster Assistance Programs, Marketing Assistance Loans, and Sugar Provisions, </DOC>
                    <PGS>42313-42335</PGS>
                    <FRDOCBP>2026-13878</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense Department</EAR>
            <HD>Defense Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Air Force Department</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Drug</EAR>
            <HD>Drug Enforcement Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Designation of Phenethyl Halides as List I Chemicals, </DOC>
                    <PGS>42392-42399</PGS>
                    <FRDOCBP>2026-13825</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Education Department</EAR>
            <HD>Education Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Charter Amendments, Establishments, Renewals and Terminations:</SJ>
                <SJDENT>
                    <SJDOC>President's Board of Advisors on Historically Black Colleges and Universities, </SJDOC>
                    <PGS>42428-42429</PGS>
                    <FRDOCBP>2026-13831</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy Department</EAR>
            <HD>Energy Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Energy Regulatory Commission</P>
            </SEE>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Zero-Based Regulating; Withdrawal, </DOC>
                    <PGS>42337-42339</PGS>
                    <FRDOCBP>2026-13875</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Charter Amendments, Establishments, Renewals and Terminations:</SJ>
                <SJDENT>
                    <SJDOC>Electricity Advisory Committee, </SJDOC>
                    <PGS>42429-42431</PGS>
                    <FRDOCBP>2026-13890</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Draft 2026 National Transmission Needs Study, </DOC>
                    <PGS>42429</PGS>
                    <FRDOCBP>2026-13844</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Environmental Protection</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Air Quality State Implementation Plans; Approvals and Promulgations:</SJ>
                <SJDENT>
                    <SJDOC>Michigan; Redesignation and Maintenance Plan for the Partial St. Clair 2010 1-Hour Sulfur Dioxide (SO2) NAAQS Nonattainment Area, </SJDOC>
                    <PGS>42356-42359</PGS>
                    <FRDOCBP>2026-13843</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Air Quality State Implementation Plans; Approvals and Promulgations:</SJ>
                <SJDENT>
                    <SJDOC>California; San Joaquin Valley; Revisions to Motor Vehicle Emissions Budgets for Ozone, </SJDOC>
                    <PGS>42399-42405</PGS>
                    <FRDOCBP>2026-13845</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>EPA Program Information on Source Water Protection, </SJDOC>
                    <PGS>42440-42441</PGS>
                    <FRDOCBP>2026-13902</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Technical Assistance Needs Assessments at Superfund Remedial or Removal Sites, </SJDOC>
                    <PGS>42439-42440</PGS>
                    <FRDOCBP>2026-13849</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Aviation</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Airspace Designations and Reporting Points:</SJ>
                <SJDENT>
                    <SJDOC>Morgantown, WV, </SJDOC>
                    <PGS>42390-42392</PGS>
                    <FRDOCBP>2026-13861</FRDOCBP>
                </SJDENT>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>The Boeing Company Airplanes, </SJDOC>
                    <PGS>42387-42390</PGS>
                    <FRDOCBP>2026-13869</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Bureau</EAR>
            <HD>Federal Bureau of Investigation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Criminal Justice Information Services Division User Fee Schedule; Correction, </DOC>
                    <PGS>42560</PGS>
                    <FRDOCBP>2026-13886</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Communications</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Advancement of the Low Power Television, TV Translator and Class A Television Service, </DOC>
                    <PGS>42359-42360</PGS>
                    <FRDOCBP>2026-13873</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Enhancing Know-Your-Upstream-Provider Requirements and Strengthening STIR/SHAKEN (Call Authentication Trust Anchor; Advanced Methods to Target and Eliminate Unlawful Robocalls), </DOC>
                    <PGS>42602-42640</PGS>
                    <FRDOCBP>2026-13874</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Emergency</EAR>
            <HD>Federal Emergency Management Agency</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Flood Hazard Determinations, </DOC>
                    <PGS>42538-42552</PGS>
                    <FRDOCBP>2026-13897</FRDOCBP>
                      
                    <FRDOCBP>2026-13898</FRDOCBP>
                      
                    <FRDOCBP>2026-13899</FRDOCBP>
                      
                    <FRDOCBP>2026-13900</FRDOCBP>
                      
                    <FRDOCBP>2026-13901</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>42434-42439</PGS>
                    <FRDOCBP>2026-13882</FRDOCBP>
                      
                    <FRDOCBP>2026-13883</FRDOCBP>
                      
                    <FRDOCBP>2026-13884</FRDOCBP>
                      
                    <FRDOCBP>2026-13885</FRDOCBP>
                </DOCENT>
                <SJ>Environmental Issues:</SJ>
                <SJDENT>
                    <SJDOC>Transwestern Pipeline Co., LLC, Planned Desert Southwest Expansion Project, </SJDOC>
                    <PGS>42431-42434</PGS>
                    <FRDOCBP>2026-13880</FRDOCBP>
                    <PRTPAGE P="iv"/>
                </SJDENT>
                <SJ>Licenses; Exemptions, Applications, Amendments, etc.:</SJ>
                <SJDENT>
                    <SJDOC>GR Catalyst Two, LLC, </SJDOC>
                    <PGS>42437</PGS>
                    <FRDOCBP>2026-13881</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Highway</EAR>
            <HD>Federal Highway Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Washington County, ME, </SJDOC>
                    <PGS>42591-42592</PGS>
                    <FRDOCBP>2026-13876</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Anti-Money Laundering and Countering the Financing of Terrorism Programs, </DOC>
                    <PGS>42363-42382</PGS>
                    <FRDOCBP>2026-13919</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>42441-42449</PGS>
                    <FRDOCBP>2026-13856</FRDOCBP>
                      
                    <FRDOCBP>2026-13857</FRDOCBP>
                      
                    <FRDOCBP>2026-13858</FRDOCBP>
                      
                    <FRDOCBP>2026-13859</FRDOCBP>
                      
                    <FRDOCBP>2026-13904</FRDOCBP>
                      
                    <FRDOCBP>2026-13905</FRDOCBP>
                      
                    <FRDOCBP>2026-13906</FRDOCBP>
                      
                    <FRDOCBP>2026-13908</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Formations of, Acquisitions by, and Mergers of Bank Holding Companies, </DOC>
                    <PGS>42445-42446</PGS>
                    <FRDOCBP>2026-13872</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Transit</EAR>
            <HD>Federal Transit Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Competitive Funding Opportunity:</SJ>
                <SJDENT>
                    <SJDOC>Fiscal Year 2026; Innovative Coordinated Access and Mobility, </SJDOC>
                    <PGS>42592</PGS>
                    <FRDOCBP>2026-13907</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fish</EAR>
            <HD>Fish and Wildlife Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Permits; Applications, Issuances, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Endangered and Threatened Species; Recovery, </SJDOC>
                    <PGS>42554-42556</PGS>
                    <FRDOCBP>2026-13850</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Incidental Take and Proposed Habitat Conservation Plan for the Sand Skink, Orange County, FL, </SJDOC>
                    <PGS>42557-42558</PGS>
                    <FRDOCBP>2026-13852</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food and Drug</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Drug Products not Withdrawn from Sale for Reasons of Safety or Effectiveness:</SJ>
                <SJDENT>
                    <SJDOC>Determination That Tovalt ODT (Zolpidem Tartrate) Orally Disintegrating Tablets, 5 Milligrams and 10 Milligrams, </SJDOC>
                    <PGS>42537</PGS>
                    <FRDOCBP>2026-13820</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Foreign Trade</EAR>
            <HD>Foreign-Trade Zones Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Application for Subzone:</SJ>
                <SJDENT>
                    <SJDOC>Kerrville Public Utility Board Public Facility Corp., Foreign-Trade Zone 155, Garwood, TX, </SJDOC>
                    <PGS>42410</PGS>
                    <FRDOCBP>2026-13893</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Sonnell Realty IV, LLC, Foreign-Trade Zone 61, Bayamon, PR, </SJDOC>
                    <PGS>42410</PGS>
                    <FRDOCBP>2026-13894</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Forest</EAR>
            <HD>Forest Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Fresno and Madera Resource Advisory Committee, </SJDOC>
                    <PGS>42408-42409</PGS>
                    <FRDOCBP>2026-13837</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Idaho Panhandle Resource Advisory Committee, </SJDOC>
                    <PGS>42408</PGS>
                    <FRDOCBP>2026-13836</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>West Virginia Resource Advisory Committee, </SJDOC>
                    <PGS>42407-42408</PGS>
                    <FRDOCBP>2026-13838</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Yavapai Resource Advisory Committee, </SJDOC>
                    <PGS>42409-42410</PGS>
                    <FRDOCBP>2026-13832</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>General Services</EAR>
            <HD>General Services Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental Impact Statements; Availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Modernization and Expansion of the Nogales DeConcini Land Port of Entry in Nogales, AZ, </SJDOC>
                    <PGS>42449-42451</PGS>
                    <FRDOCBP>2026-13871</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>Food and Drug Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Institutes of Health</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Homeland</EAR>
            <HD>Homeland Security Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Emergency Management Agency</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Housing</EAR>
            <HD>Housing and Urban Development Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>HUD-Held Healthcare Loan Sale (HLS 2026-2), </DOC>
                    <PGS>42553-42554</PGS>
                    <FRDOCBP>2026-13814</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Fish and Wildlife Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Land Management Bureau</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Internal Revenue</EAR>
            <HD>Internal Revenue Service</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Charitable Remainder Annuity Trust Listed Transaction, </DOC>
                    <PGS>42353-42356</PGS>
                    <FRDOCBP>2026-13851</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Information Reporting and Transfer for Valuable Consideration Rules for Section 1035 Exchanges of Life Insurance and Certain Other Life Insurance Contract Transactions, </DOC>
                    <PGS>42345-42353</PGS>
                    <FRDOCBP>2026-13830</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Notice of Qualified Equity Investment for New Markets Credit, </SJDOC>
                    <PGS>42594</PGS>
                    <FRDOCBP>2026-13909</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Adm</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Antidumping or Countervailing Duty Investigations, Orders, or Reviews, </DOC>
                    <PGS>42410-42425</PGS>
                    <FRDOCBP>2026-13892</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Com</EAR>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Investigations; Determinations, Modifications, and Rulings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Polypropylene Corrugated Boxes from Vietnam, </SJDOC>
                    <PGS>42559</PGS>
                    <FRDOCBP>2026-13819</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Silicon Metal from Australia and Norway, </SJDOC>
                    <PGS>42559-42560</PGS>
                    <FRDOCBP>2026-13891</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice Department</EAR>
            <HD>Justice Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Drug Enforcement Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Bureau of Investigation</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Civil Monetary Penalties for Onshore Oil and Gas Operations and Coal Trespass, </DOC>
                    <PGS>42558-42559</PGS>
                    <FRDOCBP>2026-13896</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Legal</EAR>
            <HD>Legal Services Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>42560-42561</PGS>
                    <FRDOCBP>2026-13889</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Archives</EAR>
            <HD>National Archives and Records Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>42561</PGS>
                    <FRDOCBP>2026-13879</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Credit</EAR>
            <HD>National Credit Union Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Funding Opportunity:</SJ>
                <SJDENT>
                    <SJDOC>Community Development Revolving Loan Fund, </SJDOC>
                    <PGS>42562-42564</PGS>
                    <FRDOCBP>2026-13835</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institutes of Health</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Center for Scientific Review, </SJDOC>
                    <PGS>42537-42538</PGS>
                    <FRDOCBP>2026-13864</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>
                National Oceanic
                <PRTPAGE P="v"/>
            </EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Fisheries of the Northeastern United States:</SJ>
                <SJDENT>
                    <SJDOC>2026 Chub Mackerel, Squid, and Butterfish Fishery Specifications, </SJDOC>
                    <PGS>42360-42362</PGS>
                    <FRDOCBP>2026-13867</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Science</EAR>
            <HD>National Science Foundation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Performance Review Board Members, </DOC>
                    <PGS>42564</PGS>
                    <FRDOCBP>2026-13887</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Neighborhood</EAR>
            <HD>Neighborhood Reinvestment Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>42565</PGS>
                    <FRDOCBP>2026-13863</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Personnel</EAR>
            <HD>Personnel Management Office</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Questionnaire for National Security Positions, </SJDOC>
                    <PGS>42565-42566</PGS>
                    <FRDOCBP>2026-13868</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Rural Business</EAR>
            <HD>Rural Business-Cooperative Service</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Revisions to the Biorefinery, Renewable Chemical, and Biobased Product Manufacturing Assistance Loan Program, </DOC>
                    <PGS>42335-42337</PGS>
                    <FRDOCBP>2026-13841</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Securities</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>42566, 42570-42571, 42587-42588</PGS>
                    <FRDOCBP>2026-13816</FRDOCBP>
                      
                    <FRDOCBP>2026-13817</FRDOCBP>
                      
                    <FRDOCBP>2026-13818</FRDOCBP>
                </DOCENT>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>Datum One Series Trust and Brandes Investment Partners, LP, </SJDOC>
                    <PGS>42588</PGS>
                    <FRDOCBP>2026-13822</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Datum One Series Trust and First Sentier Investors (US) LLC, </SJDOC>
                    <PGS>42588-42589</PGS>
                    <FRDOCBP>2026-13823</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Datum One Series Trust and Polar Capital LLP, </SJDOC>
                    <PGS>42584</PGS>
                    <FRDOCBP>2026-13824</FRDOCBP>
                </SJDENT>
                <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
                <SJDENT>
                    <SJDOC>Cboe BZX Exchange, Inc., </SJDOC>
                    <PGS>42566-42570</PGS>
                    <FRDOCBP>2026-13829</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Fixed Income Clearing Corp., </SJDOC>
                    <PGS>42571-42577</PGS>
                    <FRDOCBP>2026-13827</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>LCH SA, </SJDOC>
                    <PGS>42577-42584</PGS>
                    <FRDOCBP>2026-13828</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>MX2 LLC, </SJDOC>
                    <PGS>42584-42587</PGS>
                    <FRDOCBP>2026-13826</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Small Business</EAR>
            <HD>Small Business Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Disaster Declaration:</SJ>
                <SJDENT>
                    <SJDOC>Mississippi, </SJDOC>
                    <PGS>42590</PGS>
                    <FRDOCBP>2026-13853</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Wisconsin, </SJDOC>
                    <PGS>42590-42591</PGS>
                    <FRDOCBP>2026-13854</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Fiscal Year List of Requests from States or Tribes for a Small Business Administration Disaster Declaration, </DOC>
                    <PGS>42589-42590</PGS>
                    <FRDOCBP>2026-13866</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State Department</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Rescinding Portions of Department of State Title VI Regulations to Conform More Closely with the Statutory Text and to Implement Executive Order 14281, </DOC>
                    <PGS>42339-42345</PGS>
                    <FRDOCBP>2026-13860</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 Highway Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Transit Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Transportation Statistics Bureau</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Transportation Statistics</EAR>
            <HD>Transportation Statistics Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>National Census of Ferry Operators, </SJDOC>
                    <PGS>42592-42594</PGS>
                    <FRDOCBP>2026-13855</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Bureau of the Fiscal Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Internal Revenue Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Government Securities:</SJ>
                <SJDENT>
                    <SJDOC>Call for Large Position Reports, </SJDOC>
                    <PGS>42595</PGS>
                    <FRDOCBP>2026-13862</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veteran Affairs</EAR>
            <HD>Veterans Affairs Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Joint Brain, Behavioral, and Mental Health and Medical Health Scientific Merit Review Board, </SJDOC>
                    <PGS>42599</PGS>
                    <FRDOCBP>2026-13833</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Privacy Act; Systems of Records, </DOC>
                    <PGS>42595-42599</PGS>
                    <FRDOCBP>2026-13846</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Federal Communications Commission, </DOC>
                <PGS>42602-42640</PGS>
                <FRDOCBP>2026-13874</FRDOCBP>
            </DOCENT>
        </PTS>
        <AIDS>
            <HD SOURCE="HED">Reader Aids</HD>
            <P>Consult the Reader Aids section at the end of this issue for phone numbers, online resources, finding aids, and notice of recently enacted public laws.</P>
            <P>To subscribe to the Federal Register Table of Contents electronic mailing list, go to https://public.govdelivery.com/accounts/USGPOOFR/subscriber/new, enter your e-mail address, then follow the instructions to join, leave, or manage your subscription.</P>
        </AIDS>
    </CNTNTS>
    <VOL>91</VOL>
    <NO>130</NO>
    <DATE>Thursday, July 9, 2026</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="42313"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Commodity Credit Corporation</SUBAGY>
                <CFR>7 CFR Parts 1412, 1416, 1421, 1427, 1430, 1434, and 1435</CFR>
                <DEPDOC>[Docket ID FSA-2026-0067]</DEPDOC>
                <RIN>RIN 0560-AI84</RIN>
                <SUBJECT>Supplemental Disaster Assistance Programs, Marketing Assistance Loans, and Sugar Provisions</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Commodity Credit Corporation, Farm Service Agency (FSA), U.S. Department of Agriculture (USDA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This rule revises the regulations of the Emergency Assistance for Livestock, Honeybees, and Farm-Raised Fish Program (ELAP), the Livestock Forage Disaster Program (LFP), the Livestock Indemnity Program (LIP), the Tree Assistance Program (TAP), the Marketing Assistance Loan (MAL) and Loan Deficiency Payments (LDP) Programs, and the Sugar Program to conform with provisions of the One Big Beautiful Bill Act (OBBBA). Changes to the supplemental disaster assistance programs include ELAP assistance for losses due to bird depredation and a change to honeybee colony loss normal mortality; a lower drought threshold for LFP eligibility; LIP assistance for unborn death losses and changes to compensation for predation losses and the market values used in the LIP payment calculations; and changes to the TAP eligibility threshold and reimbursement percentage for certain costs. This rule increases the MAL and LDP loan rates for all eligible commodities for the 2026 through 2031 crop years as specified by OBBBA. Additional MAL and LDP changes for upland and extra-long staple (ELS) cotton required by OBBBA include revised formulas to calculate the prevailing world market price for upland cotton, the introduction of a prevailing world market price and adjusted world price for ELS cotton, and changes to the payment of cotton storage costs by area. Additionally, FSA is amending regulations to add provisions for a 30-day post-repayment loan review in which a refund for upland cotton repayment or an additional LDP disbursement could occur. Sugar Program changes are related to effective loan rates, storage rates, and sugar marketing allocation provisions. This rule also makes minor administrative changes to the Sugar Program regulations. Technical amendments are included for grains and similarly handled commodities, and honey. This rule also makes additional changes to the regulations for those programs to update eligibility and payment provisions, clarify program requirements, and improve program integrity. This rule also updates the Feedstock Flexibility Program (FFP) provisions to indicate that 2026 is the final crop year covered by the program, and makes corrections to the regulations for the Agriculture Risk Coverage (ARC) and Price Loss Coverage (PLC) Programs and Dairy Margin Coverage (DMC) Program.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective on July 9, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For ELAP, Seth Cross; telephone: (402) 309-3338; or email: Seth.C
                        <E T="03">ross@usda.gov.</E>
                         For LFP and LIP, Kelly Breinig; telephone: (202) 774-7437; email: 
                        <E T="03">Kelly.Breinig@usda.gov.</E>
                         For TAP, Jenae Orso; telephone: (229) 850-0194; or email: 
                        <E T="03">Jenae.Prescott@usda.gov.</E>
                         For MAL and LDP, Shayla Watson; telephone: (202) 690-2350; or email: 
                        <E T="03">Shayla.Watson@usda.gov.</E>
                         For cotton provisions, Dana Wood; telephone: (202) 692-5288; or email: 
                        <E T="03">Dana.Wood@usda.gov.</E>
                         For the Sugar Program, Shanita Landon; telephone: (202) 690-1612; or email: 
                        <E T="03">Shanita.Landon@usda.gov;</E>
                         and Carlann Unger; telephone: (773) 573-5163; or email: 
                        <E T="03">Carlann.Unger@usda.gov.</E>
                         For ARC and PLC, Jamie Garriott; telephone: (202) 253-9843; or email: 
                        <E T="03">Jamie.Garriott@usda.gov.</E>
                         For DMC, Douglas E. Kilgore; telephone: (717) 887-0963; or email: 
                        <E T="03">Douglas.E.Kilgore@usda.gov.</E>
                         Individuals with disabilities who require alternative means for communication should contact the USDA Target Center at (202) 720-2600 (voice and text telephone (TTY mode)) or dial 711 for Telecommunications Relay Service (both voice and text telephone users can initiate this call from any telephone).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Background</FP>
                    <FP SOURCE="FP-2">II. Supplemental Disaster Assistance Programs</FP>
                    <FP SOURCE="FP1-2">A. ELAP</FP>
                    <FP SOURCE="FP1-2">1. Assistance for Losses Due to Bird Depredation</FP>
                    <FP SOURCE="FP1-2">2. Honeybee Colony Loss Normal Mortality</FP>
                    <FP SOURCE="FP1-2">3. Assistance for Transportation Costs</FP>
                    <FP SOURCE="FP1-2">4. Other Changes</FP>
                    <FP SOURCE="FP1-2">B. LFP</FP>
                    <FP SOURCE="FP1-2">C. LIP</FP>
                    <FP SOURCE="FP1-2">1. Assistance for Unborn Death Losses</FP>
                    <FP SOURCE="FP1-2">i. Background</FP>
                    <FP SOURCE="FP1-2">ii. Implementation for Program Year 2026 and Subsequent Years</FP>
                    <FP SOURCE="FP1-2">iii. Implementation for Program Years 2024 and 2025</FP>
                    <FP SOURCE="FP1-2">2. Updates to Compensation for Predation Losses to 100 Percent of Market Values</FP>
                    <FP SOURCE="FP1-2">3. Updates to Market Values Used in Payment Calculations, Including Adding a Producer's Alternative Price Option</FP>
                    <FP SOURCE="FP1-2">4. Other Changes</FP>
                    <FP SOURCE="FP1-2">D. TAP</FP>
                    <FP SOURCE="FP-2">III. Marketing Assistance Loans and Loan Deficiency Payments</FP>
                    <FP SOURCE="FP1-2">A. Honey Nonrecourse Loans</FP>
                    <FP SOURCE="FP1-2">B. Upland and ELS Cotton</FP>
                    <FP SOURCE="FP1-2">1. Payment of Cotton Storage Costs</FP>
                    <FP SOURCE="FP1-2">2. Upland Cotton Prevailing World Market Price Change</FP>
                    <FP SOURCE="FP1-2">3. ELS Prevailing World Market Price Calculation</FP>
                    <FP SOURCE="FP1-2">4. 30-Day Loan Optimization Window (LOW) for Upland Cotton</FP>
                    <FP SOURCE="FP1-2">5. Additional Changes for Cotton</FP>
                    <FP SOURCE="FP1-2">C. Sugar Program</FP>
                    <FP SOURCE="FP1-2">D. Feedstock Flexibility Program</FP>
                    <FP SOURCE="FP-2">IV. ARC and PLC Correction</FP>
                    <FP SOURCE="FP-2">V. DMC Correction</FP>
                    <FP SOURCE="FP-2">VI. Severability</FP>
                    <FP SOURCE="FP-2">VII. Regulatory Analyses</FP>
                    <FP SOURCE="FP1-2">A. Effective Date, Notice and Comment, and Paperwork Reduction Act</FP>
                    <FP SOURCE="FP1-2">B. Executive Orders 12866, 13563, and 14192</FP>
                    <FP SOURCE="FP1-2">C. Cost Benefit Analysis Summary</FP>
                    <FP SOURCE="FP1-2">D. Environmental Review</FP>
                    <FP SOURCE="FP1-2">E. Executive Order 13175</FP>
                    <FP SOURCE="FP1-2">F. Unfunded Mandates Reform Act</FP>
                    <FP SOURCE="FP1-2">G. E-Government Act Compliance</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    On July 4, 2025, President Trump signed into law H.R. 1 (Pub. L. 119-21), also known as the One Big Beautiful Bill Act (OBBBA). This rule amends the provisions of the supplemental disaster assistance programs (ELAP, LFP, LIP, and TAP), MAL, LDP, and the Sugar 
                    <PRTPAGE P="42314"/>
                    Program to implement changes made by OBBBA. This rule also makes discretionary changes to those programs to improve program administration and clarify existing policy, in addition to minor administrative changes such as updating references to the applicable program years and removing outdated provisions.
                </P>
                <P>CCC is updating the regulations for the supplemental disaster assistance programs as mandated by OBBBA. These updates include ELAP assistance for losses due to bird depredation and a change to honeybee colony loss normal mortality, a lower drought threshold for LFP eligibility, LIP assistance for unborn death losses and changes to compensation for predation losses and the market values used in the LIP payment calculations, and changes to the TAP eligibility threshold and reimbursement percentage for certain costs. This rule also makes additional changes to the regulations for these programs to clarify program provisions and requirements and improve program integrity.</P>
                <P>This rule increases the MAL and LDP loan rates for all eligible commodities for the 2026 through 2031 crop years as specified by OBBBA. Additional MAL and LDP changes for upland and extra-long staple (ELS) cotton required by OBBBA include revised formulas to calculate the prevailing world market price for upland cotton, the introduction of a prevailing world market price and adjusted world price for ELS cotton, and changes to the payment of cotton storage costs by area. Additionally, CCC is amending the regulations to add provisions for a 30-day post-repayment loan review in which a refund for upland cotton repayment or an additional LDP disbursement could occur. Sugar Program changes are related to effective loan rates, storage rates, and sugar marketing allocation provisions. This rule also makes minor administrative changes to the Sugar Program regulations. Technical amendments are included for grains and similarly handled commodities and honey. This rule updates the Feedstock Flexibility Program (FFP) provisions to indicate that 2026 is the final crop year covered by the program. This rule also amends definitions in the ARC and PLC regulation and corrects a cross-reference in the DMC regulation.</P>
                <HD SOURCE="HD1">II. Supplemental Agricultural Disaster Assistance Programs</HD>
                <P>ELAP, LFP, LIP, and TAP were authorized by section 1501 of the Agricultural Act of 2014 (Pub. L. 113-79, 7 U.S.C. 9081). Section 10401 of OBBBA included mandatory changes for each of these programs. This rule implements those changes and includes additional discretionary changes for these programs.</P>
                <P>This rule also amends the general administrative provisions for the supplemental agricultural disaster assistance programs in 7 CFR 1416.2, subpart A, for consistency with other FSA and CCC programs and updates references to USDA's debt management provisions, which are provided in 7 CFR part 3. CCC previously issued a rule on June 2, 2026 (91 FR 32880) to implement changes to the payment limitation provisions for qualified pass-through entities and average adjusted gross income (AGI) limitation provisions that were mandated by OBBBA. This rule revises § 1416.6 to remove outdated payment limitation and AGI provisions and to refer to the current provisions in 7 CFR part 1400.</P>
                <HD SOURCE="HD2">A. ELAP</HD>
                <P>ELAP provides financial assistance to eligible producers of livestock, honeybees, and farm-raised fish for losses due to disease, certain adverse weather events, or loss conditions, including blizzards and wildfires, as determined by the CCC. In accordance with section 10401(c) of OBBBA, this rule amends the ELAP regulations to add provisions for losses due to bird depredation and establish a honeybee normal mortality rate for determining eligible honeybee colony losses. It also makes additional discretionary changes including adding definitions for terms related to transportation assistance and other minor updates for clarity and consistency.</P>
                <HD SOURCE="HD3">1. Assistance for Losses Due to Bird Depredation</HD>
                <P>This rule amends the ELAP regulations to conform with OBBBA provisions that provide assistance for freshwater farm-raised fish damage or loss due to bird depredation, which were not previously covered under ELAP. OBBBA provides that the payment rate for this assistance will take the following factors into account: (1) costs associated with the deterrence of piscivorous birds; (2) the value of lost fish and revenue due to bird depredation; and (3) costs associated with disease loss from bird depredation. OBBBA specifies that the minimum payment rate shall be not less than $600 per acre of farm-raised fish. As provided in this final rule at § 1416.109(e), for program year 2026, CCC has determined that the payment rate will be $600 per eligible acre because CCC does not have data to justify increasing the payment rate above the minimum rate at this time. CCC may increase the rate per acre in future program years if there is documented evidence justifying an increase in the payment rate. For example, CCC welcomes information from independent third-parties, such as a university or cooperative extension service with expertise related to the farm-raised fish industry, that provides documented evidence relating to the costs associated with the deterrence of piscivorous birds, the value of lost fish and revenue due to bird depredation, and costs associated with disease loss from bird depredation. A producer may earn only $600 per eligible acre for each program year; repeated bird depredation events during a year will not result in multiple payments for the same acres. The payment rate is applicable for all eligible farm-raised fish.</P>
                <P>
                    In accordance with section 10401(c) of OBBBA, payments for eligible losses due to bird depredation will be equal to the applicable payment rate described above, multiplied by 85 percent of the total number of acres of farm-raised fish farms that the producer has in production for the calendar year (referred to as the “program year” in the ELAP regulations). This rule adds that payment calculation in § 1416.112(c). To be considered eligible acres, the producer must have reported them to FSA on a timely filed acreage report 
                    <SU>1</SU>
                    <FTREF/>
                     in accordance with 7 CFR part 718, as determined by CCC, and they must have been in use for fish production at the time of bird depredation (§ 1416.103(k)). Unused ponds or waterways, bodies of water not under control of the producer, and any water that is reduced due to drought are not eligible acres for bird depredation losses.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Collection of acreage reports for administration of ELAP is exempt from the Paperwork Reduction Act (44 U.S.C. chapter 35) as specified in 7 U.S.C. 9091(c)(2).
                    </P>
                </FTNT>
                <P>
                    In order to administer assistance for losses due to bird depredation, CCC is also adding and amending several definitions in § 1416.102. This rule adds definitions of “bird depredation”, in alignment with OBBBA, and “freshwater” for clarity. It also amends the definition of “eligible loss condition” to include bird depredation. This rule updates the definition of “farm-raised fish” to specify that, for the purpose of loss due to bird depredation, the term means “fish propagated and reared in a controlled freshwater environment” as provided by OBBBA and clarifies that it does not include crawfish or crayfish for that purpose. Crawfish and crayfish are excluded from “farm-raised fish” for losses due to bird depredation because they are 
                    <PRTPAGE P="42315"/>
                    crustaceans, not fish, and producers do not have a standard method to track crawfish and crayfish inventory. Residual inventory from prior years is often present, and producers cannot accurately track current inventory because crawfish and crayfish lay hundreds of eggs, which are not hatched prior to seeding.
                </P>
                <P>To be eligible for payment, a producer must have produced eligible farm-raised fish for commercial use as part of a farming operation and must have had a loss due to bird depredation, as described above (§ 1416.105(d)). The farm-raised fish must be propagated or reared in a controlled freshwater environment, have been maintained for commercial use as part of the farming operation, and have been physically located in the county where the piscivorous birds were present on the beginning day of the loss condition (§ 1416.104(f)(3)).</P>
                <P>To apply for losses due to bird depredation, a producer must timely file an acreage report as provided in 7 CFR part 718. By March 1 of the following program year, the producer must also file a notice of loss, an Emergency Loss Assistance for Farm-Raised Fish Application, a report indicating eligible acres of freshwater in use at the time of bird depredation, and an active U.S. Fish and Wildlife Depredation permit with cormorant, American white pelican, heron, or Great egret listed on the permit. If requested by FSA, the producer must also submit documentation to substantiate the producer's use of eligible acres of freshwater reported, inventory losses, and a minimum of 3 of the following 5 items:</P>
                <P>• Documentation that losses are from bird depredation, supported by evidence including bird sightings, fish mortality records, aerial surveys, or third-party assessments;</P>
                <P>• Documentation of annual expenditures on non-lethal and lethal methods to prevent or reduce bird presence in the area;</P>
                <P>• Documentation of costs attributed to disease spread by birds, including prescriptions for medicated feed or any other costs showing disease loss from bird depredation;</P>
                <P>• A USDA-Wildlife Services or U.S. Fish and Wildlife Service approved bird harassment plan; and</P>
                <P>• A year-end collecting report of the number of birds terminated and reported to the U.S. Fish and Wildlife Service.</P>
                <HD SOURCE="HD3">2. Honeybee Colony Loss Normal Mortality</HD>
                <P>Section 10401(c) of OBBBA (7 U.S.C. 9081(d)) provides that a normal mortality rate of 15 percent will be used with respect to eligible honeybee colony losses. Prior to this change, the normal mortality rate was established by FSA for each program year based on published data. This rule updates § 1416.111(b)(2) to conform with OBBBA and specifies the normal mortality rate of 15 percent for program year 2026 and subsequent years.</P>
                <HD SOURCE="HD3">3. Assistance for Transportation Costs</HD>
                <P>CCC is adding definitions of “harvested feed or feedstuffs,” “miles above normal,” and “truckload” to clarify provisions related to assistance for transportation costs and improve program integrity. As provided in the definition, “harvested feed or feedstuffs” includes mechanically harvested production that must be wrapped, twined, stacked, or combined in a manner that the harvested product can be transported from one area to another, which aligns with the definition of “harvested” under the Noninsured Crop Disaster Assistance Program (NAP; § 1437.3). This definition is intended to alleviate confusion in situations where a producer has cut a crop but has not further processed it into a condition that allows it to be removed from the field. It clarifies that windrows that have not been mechanically processed into a transportable state are not considered harvested. Similarly, straw left in the field that has not been mechanically processed is also not considered harvested.</P>
                <P>The definition of “truckload” and new § 1416.110(r) are intended to clarify how FSA will determine eligibility for payment for feed or livestock transportation. The truckload definition specifies that the transportation must be by a motorized land vehicle, which does not include trains, planes, or ships. A truckload is considered a single trip and includes only the mileage from one point to another, not multiple end points or more than one stop. It also excludes mileage for delivery that is not clearly identified by the mileage rate on verifiable documentation. In addition, the definition and § 1416.110(r) exclude transportation provided through services such as the U.S. Postal Service, FedEx, and UPS. Fees from these transportation service providers are considered part of a commercial shipping service and therefore do not qualify as personal vehicle mileage or an eligible trucking-rate expense.</P>
                <P>The definition of “miles above normal” specifies that the term only includes transportation from one point to another, and does not include multiple end points where items are offloaded and then reloaded for transport to additional locations. It also clarifies that eligibility requires verifiable documentation that delineates a mileage rate that is quantitatively separate from the price of the feed or animals being transported. This definition has been added to remove confusion in situations where a producer pays for the transport of feed or animals, but the vendor incorporates transportation costs into the total price and does not separately identify the miles above normal used to calculate ELAP assistance.</P>
                <HD SOURCE="HD3">4. Other Changes</HD>
                <P>This rule amends § 1416.110(a) to specify that livestock feed payments for an eligible livestock producer will be calculated based on losses for no more than 150 grazing days during the program year. The clarification of “grazing” days was previously omitted from the regulation and this addition provides consistency with payments for grazing losses in §  1416.110(g)(2).</P>
                <P>This rule also amends the definition of “program year” for clarity and removes unnecessary references to prior years. CCC is adding definitions of “adult water buffalo bull”, “adult water buffalo cow” and “non-adult water buffalo” in § 1416.102 and adding adult and non-adult water buffalo as separate categories of livestock in § 1416.104. Water buffalo were previously considered eligible under the categories for adult and non-adult buffalo; this change is intended to improve clarity and reduce confusion. This rule also amends § 1416.106 to update the provisions for applications for payment for honeybees and farm-raised fish, which now use separate application forms.</P>
                <P>
                    CCC is revising § 1416.107(a) to clarify the requirement to file an acreage report. Acreage reports are required by § 1416.106, and they must be filed in accordance with the provisions of §§ 718.101 through 718.112 that generally apply to FSA and CCC programs. As provided in § 718.101(c), acreage reports must be filed by the final reporting date established by the Deputy Administrator, and late-filed acreage reports are subject to the provisions of § 718.104. CCC is also adding § 1416.107(b) to provide the deadline for producers to submit any additional documentation requested by CCC to verify the producer's eligibility or losses. Such documentation must be 
                    <PRTPAGE P="42316"/>
                    provided by a producer by the later of March 1 after the end of the applicable program year or 60 days after the date of the request. This rule also amends paragraph references throughout the regulations where necessary due to the changes discussed above.
                </P>
                <HD SOURCE="HD2">B. LFP</HD>
                <P>LFP provides financial assistance to livestock producers who suffer eligible grazing losses due to a qualifying drought during the normal grazing period or when a Federal agency prohibits grazing the normal permitted livestock on managed rangeland due to a qualifying fire. LFP payments for drought are based on the drought severity, as determined in accordance with the U.S. Drought Monitor. Section 10401(b) of OBBBA (7 U.S.C. 9081) lowered the drought threshold for program eligibility.</P>
                <P>Prior to this rule, LFP eligibility required eight consecutive weeks of qualifying severe drought (D2) intensity during the normal grazing period before livestock producers were eligible for drought assistance. OBBBA lowered this threshold to four consecutive weeks of qualifying severe drought (D2) conditions for program eligibility in order for a producer to receive a one-month payment. OBBBA also adds eligibility for a two-month payment if severe drought (D2) conditions continue for 7 out of 8 consecutive weeks during the normal grazing period. All other drought intensities, durations, and payment months for LFP eligibility remain the same. These changes will be effective for program year 2026 and subsequent years.</P>
                <P>CCC is adding definitions of “adult water buffalo bull”, “adult water buffalo cow” and “non-adult water buffalo” in § 1416.202 and adding adult and non-adult water buffalo as separate categories of covered livestock in § 1416.204(b). Water buffalo were previously considered eligible under the categories for adult and non-adult buffalo; this change is intended to improve clarity and reduce confusion.</P>
                <HD SOURCE="HD2">C. LIP</HD>
                <P>As authorized by section 1501(b) of the Agricultural Act of 2014 (7 U.S.C. 9081(b)), LIP provides financial assistance to eligible livestock producers for eligible death losses, in excess of normal mortality, caused by an eligible cause of loss, including adverse weather, disease, and attacks by animals reintroduced into the wild by the Federal government or protected by Federal law. The program also compensates eligible livestock owners who sell livestock at reduced prices due to injury from an eligible loss condition.</P>
                <HD SOURCE="HD3">1. Assistance for Unborn Death Losses</HD>
                <HD SOURCE="HD3">i. Background</HD>
                <P>As mandated by section 10401(a)(2) (7 U.S.C. 9081(b)) of OBBBA, this rule adds provisions to provide compensation to eligible livestock producers for unborn livestock death losses, in excess of normal mortality, that occurred on or after January 1, 2024. Unborn death loss compensation is determined based on losses of eligible adult livestock that were gestating on the date of their death due to an eligible loss condition. Livestock sold due to injury from an eligible loss event and livestock that are stillborn or aborted from adult females that did not die as a result of an eligible loss event are not eligible for unborn death loss compensation.</P>
                <P>Section 10401(a)(2) (7 U.S.C. 9081(b)) of OBBBA requires that payments for unborn death losses will be compensated at a rate that is less than or equal to 85 percent of the payment rate established with respect to the lowest weight class of the same kind and type of livestock. As required by OBBBA, the payment amount will be equal to that payment rate multiplied by an applicable number, referred to in this rule as the “birthing factor” (7 U.S.C. 9081(b)(5)(C)). OBBBA established the birthing factors for cattle, bison, horses, sheep, and swine. For other species of livestock, OBBBA requires that the birthing factor for such livestock would be the average number of birthed animals per gestational cycle for each species. This rule adds these birthing factors to § 1416.306(i). Unborn death losses will be compensated based on the number of eligible adult females that were gestating at the time of the adult female livestock's death, after normal mortality has been applied; no additional normal mortality reductions will apply to unborn death losses.</P>
                <P>Eligible livestock categories for unborn death losses include alpacas, beef cattle, beefalo, buffalo, bison, caribou (reindeer), dairy cattle, deer, elk, equine, goats, llamas, sheep, swine, and water buffalo, or other species. Historically, the eligible livestock categories for LIP have been identified by livestock kind, type (adults, non-adults, including sex), and weight class, as applicable, for beef cattle, beefalo, buffalo, bison, dairy cattle, goats, sheep, and water buffalo; however, losses of alpacas, caribou, deer, elk, equine, and llamas have been reported under a single category for each livestock kind that encompasses all adults, non-adults, sexes, and weight ranges due to that livestock kind's limited market data and low program participation. Swine have been identified by types and weights of livestock; however, they have not been separately identified by sex.</P>
                <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="s30,r100,r100">
                    <TTITLE>Table 1—Examples of Livestock Kind, Type, and Weight Class Structure Established for LIP Prior to OBBBA Implementation</TTITLE>
                    <BOXHD>
                        <CHED H="1">Livestock kind</CHED>
                        <CHED H="1">Type</CHED>
                        <CHED H="1">Weight class</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Alpacas</ENT>
                        <ENT>All</ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Beef Cattle</ENT>
                        <ENT>Adult</ENT>
                        <ENT>Bull.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>Cow.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Non-adult</ENT>
                        <ENT>Less than 400 pounds.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>400 pounds or more.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Swine</ENT>
                        <ENT>Suckling/Nursery Pigs</ENT>
                        <ENT>Less than 50 pounds.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Lightweight Barrows/Gilts</ENT>
                        <ENT>50 to 150 pounds.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Sows/Boars/Barrows/Gilts</ENT>
                        <ENT>151 to 450 pounds.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Boars/Sows</ENT>
                        <ENT>451 pounds or more.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    OBBBA provides that eligible livestock producers will be compensated for eligible unborn livestock death losses that occurred on or after January 1, 2024. As discussed below, to administer this assistance, CCC is updating the way livestock are categorized for 2026 and subsequent years to collect additional information that is relevant to determining unborn livestock death losses. For the 2024 and 2025 program (calendar) years, FSA will 
                    <PRTPAGE P="42317"/>
                    use information that was previously reported, as described below.
                </P>
                <HD SOURCE="HD3">ii. Implementation for Program Year 2026 and Subsequent Years</HD>
                <P>Beginning in program year 2026, CCC will update the livestock categories for livestock kinds that were previously reported under a single category, establishing payment rates separately for adults and non-adults using national market data that is available. For those categories that lack ample market data, CCC will use a comparative model of the price ratios between adults and non-adults for other livestock categories that do have ample market data, as applicable. For example, the ratio between the 2025 payment rate for an adult beef cow ($1,810.09) to the payment rate of non-adult beef cattle-less than 400 pounds ($770.86) is 43 percent or a 43:100 ratio. An example of when this scenario could be used is to establish payment rates for alpacas when no market data are available to establish a non-adult rate.</P>
                <P>This rule amends the definitions in § 1416.302 to establish separate definitions for adult and non-adult livestock for livestock kinds that were previously reported under a single category and updates the category list to reflect those defined terms in § 1416.304. Form CCC-852, LIP Application for Payment, has been updated to allow producers to certify the number of eligible adult female livestock death losses for livestock that were bred and gestating at the time of the adult female livestock's death. This update enables payments to be calculated for unborn livestock death losses based on the number of eligible adult bred female death losses, after applying normal mortality adjustments. As defined in § 1416.302, “bred” means that an eligible adult female livestock has been exposed to an adult male breeding animal and is gestating or deliberately bred through controlled reproduction. This term does not apply to poultry. Payments will be based on the number of eligible adult bred female death losses identified by the producer on the Application For Payment—livestock producers typically use the term “bred” rather than “gestating” when identifying pregnant livestock and track breeding dates and expected gestation status in accordance with the producer's specific breeding practices for their operation rather than confirmed gestation.</P>
                <P>CCC may request additional supporting documentation from eligible livestock producers or conduct spot checks to confirm that livestock were gestating at the time of the eligible loss of the adult female. Additional information that may be requested includes, but is not limited to, verification of breeding records, exposure dates, herd health or veterinary documentation, inventory logs, and other supporting operational records consistent with the producer's normal business practices. A spot check or request for additional information is appropriate when CCC identifies any of the following:</P>
                <P>• Missing, inconsistent, or incomplete breeding or inventory records;</P>
                <P>• Reported death losses that appear excessive or outside normal expectations for the operation type, size, or production practices;</P>
                <P>• Conflicting information between the application, supporting documentation, or prior-year program participation;</P>
                <P>• Patterns of repeated corrections, revisions, or documentation gaps by the producer; or</P>
                <P>• Situations where CCC has reason to question whether livestock were bred at the time of loss based on reported exposure dates, breeding windows, or herd management practices.</P>
                <P>If discrepancies are identified, further documentation may be requested and adjustments may be made to approved death loss numbers.</P>
                <P>Payment rates for unborn livestock death losses will be 85 percent of the lowest non-adult weight class, as applicable, of the same livestock kind; this is the maximum payment rate authorized by OBBBA.</P>
                <HD SOURCE="HD3">iii. Implementation for Program Years 2024 and 2025</HD>
                <P>The application periods for the 2024 and 2025 program (calendar) years have ended, and CCC's implementation of this provision is intended to minimize the burden on producers who have previously applied for LIP compensation for the adult female in those prior years. To implement this provision retroactively for the 2024 and 2025 program years, CCC is using a two-pronged approach: one approach for eligible livestock categories where producer data on file already identifies eligible adult female losses, and another for livestock categories for which losses of adults, non-adults, males, and females were reported collectively and not identified by type.</P>
                <P>For program years 2024 and 2025, FSA records indicate that approximately 4,400 LIP applications have been approved that may require review for unborn death losses. CCC has established LIP payment rates based on livestock kind, type, and weight range for the categories of adult beef, beefalo, bison, buffalo, dairy, and water buffalo cows, nanny goats, and ewes (sheep); as a result, CCC can identify all eligible adult female livestock death losses, after normal mortality, from producers' approved applications. However, CCC does not have the data on file to identify the number of those adult females that were gestating at the time of death. Additionally, CCC can identify all approved eligible losses for livestock categories for which adults, non-adults, males, and females were combined, as applicable, but cannot identify the number of eligible adult females included in those losses.</P>
                <P>CCC evaluated the operational challenges of implementing this provision retroactively because all 2024 and 2025 LIP applications would need to be reviewed and revised to indicate whether livestock were female and, if applicable, gestating at the time of death. Instead, CCC reviewed available loss data and typical breeding and disaster patterns to determine an approach based on the best available data. Records show that 86 percent of LIP applications submitted for these program years were for beef cattle losses, and within this category, CCC can identify adult female losses classified as “adult beef cow.” Furthermore, FSA records indicate that 52 percent of eligible loss events in 2024 and 2025 occurred in January, February, and March; this period typically aligns with beef cow gestation in preparation for late winter and spring calving. Under U.S. commercial livestock production practices, breeding females of major livestock species are typically gestating for a substantial portion of the calendar year, commonly more than half the year and, for some species, approaching three-quarters or more (including beef and dairy cattle). Requiring producers to self-certify bred livestock or submit breeding records for 2024 and 2025 losses—information not previously required for LIP participation—would create significant administrative burden and impede timely delivery of critical disaster assistance authorized by OBBBA. These considerations support CCC's decision for 2024 and 2025 to focus on livestock categories where accurate identification is feasible and to apply reasonable assumptions regarding timing and gestation while maintaining program integrity and minimizing producer burden and operational risk.</P>
                <P>
                    Accordingly, rather than requiring all producers to revise their 2024 or 2025 LIP application to identify which females were bred at the time of death, CCC will implement a streamlined approach in 2024 and 2025 for 
                    <PRTPAGE P="42318"/>
                    producers who reported losses for livestock categories for which the number of eligible adult female livestock is already on file. Based on the rationale and analysis of the timing of loss events, and the livestock categories experiencing the losses, all approved female livestock deaths in 2024 and 2025 will be presumed gestating at the time of loss, and CCC will automatically issue an unborn livestock death loss payment to the applicant based on the number of eligible adult female losses after normal mortality has been applied. No additional action is required by the LIP applicant to receive this payment. The payment for these specific livestock categories will be calculated at 85 percent of the payment rate of the lowest weight range category established for the applicable livestock, multiplied by the applicable birthing factor.
                </P>
                <P>Losses for livestock categories for which adults, non-adults, males, and females were reported collectively, and for which livestock types were not separated by sex for program years 2024 and 2025, account for approximately 100 applications, primarily for deer, elk, equine, and llamas. These species have gestational periods ranging from roughly 200 days to 11 months. Because CCC does not have data to determine how many of these losses were female, applicants with approved losses in these categories may revise their previously approved 2024 and 2025 CCC-852 LIP applications to identify the number of adult females included in their reported losses. Swine have established adult livestock types that combine boars and sows, and they also have established payment rates for adults and non-adults. Applications for these types for program years 2024 and 2025 will need to be revised to identify females specifically. Other revisions to 2024 and 2025 applications, such as any increases to adult livestock losses, are not authorized.</P>
                <P>To maintain consistency across the two reporting situations (those who have identified livestock deaths by gender at the time of adult female loss and those who have reported collectively without separating by gender), CCC will only require identification of female losses retroactively for the latter group and will not request additional documentation or proof of breeding status for either group. Once producers identify female livestock and the revised application is reviewed and determined to be accurate, CCC may issue an additional payment to compensate for unborn death losses. With the exception of swine, this payment will be based on the newly determined eligible female losses after normal mortality and will be calculated at 40 percent of the payment rate, since the payment rate for these categories includes both adults and non-adults and does not have an established lower weight class rate. This 40 percent factor was determined using similar ratios of adult and non-adult LIP payment rates in other livestock categories. Swine that are newly identified as sows will be compensated at 85 percent of the lowest weight category already established (sucklings or nursery pigs). The payment calculation will also incorporate the applicable birthing factor that accounts for the average number of offspring per birthing cycle.</P>
                <P>For applications that require identification of female losses to receive a payment for unborn livestock death losses, FSA will notify all eligible producers of the opportunity to submit revisions to their approved 2024 or 2025 LIP applications by an established deadline. Any applications that are not revised by this deadline will remain unchanged, and no additional payment will be issued. CCC is not extending the original deadlines to submit an application for these years, and no other revisions to approved applications are authorized.</P>
                <HD SOURCE="HD3">2. Updates to Compensation for Predation Losses to 100 Percent of Market Values</HD>
                <P>Section 10401(a) of OBBBA (7 U.S.C. 9081(b)) required changes to the payment calculation for eligible livestock losses due to predation, which includes attacks by animals reintroduced into the wild by the Federal Government or protected by Federal law, including wolves and avian predators. Previously, losses due to predation were compensated at 75 percent of the market value established by CCC. Under OBBBA, losses due to predation must be compensated at 100 percent of the market value as determined by CCC. CCC has added § 1416.306(d) and (f) to provide the updated payment calculation for predation losses and will implement this change starting with the 2026 program year.</P>
                <HD SOURCE="HD3">3. Updates to Market Values Used in Payment Calculations, Including Adding a Producer's Alternative Price Option</HD>
                <P>Section 10401(a) of OBBBA (7 U.S.C. 9081(b)) amends the Agricultural Act of 2014 to require that indemnity payments to eligible producers must be based on the applicable percentage of the market value of the affected livestock on the “applicable date,” as determined by CCC. In accordance with these OBBBA amendments, the “applicable date” is defined as “the day before the date of death of the livestock” or “the day before the date of the event that caused the harm to the livestock that resulted in a reduced sale price.” Since LIP began, the daily market prices have not been established because consistent market data and resources are not available for most livestock kinds, types, and weight classes. Therefore, payment rates have been set nationally using the previous year's national average market data from USDA's National Agricultural Statistical Service (NASS) or Agricultural Marketing Service (AMS) for most livestock species.</P>
                <P>OBBBA includes provisions that allow producers to document regional price premiums that exceed the national average market price established by CCC. Beginning with the 2026 program year, CCC will enhance the process for establishing LIP payment rates to better reflect accurate market values for eligible livestock categories. CCC will continue to set national payment rates using national average market data, but will also provide additional options to allow compensation to be based on the highest of the following:</P>
                <P>• National average market value by livestock kind, type, and weight class at the beginning of the program year, based on prior-year market data as determined by CCC;</P>
                <P>• National average market value by livestock kind, type, and weight class at the end of the program year, based on current-year market data as determined by CCC;</P>
                <P>• The producer's verifiable market value for livestock of the same kind, type, and weight class, based on the market value closest to the date of loss or date of event that caused the injury, specific to the producer's operation and program year, not to exceed 145 percent of the higher of the national average market values established by CCC; or</P>
                <P>• Another price approved by CCC on data showing market value the day before the livestock loss or the day before the date of the event that caused the loss.</P>
                <FP>
                    Effective for 2026 and subsequent program years, LIP payment rates are based on the higher of the national average market values determined by CCC or the producer's approved alternative market value, not to exceed 145 percent of the national average market value. The determined market values are multiplied by 75 percent for losses due to an eligible adverse weather 
                    <PRTPAGE P="42319"/>
                    event or disease, and 100 percent for losses due to an eligible attack.
                </FP>
                <P>For 2026 and subsequent program years, CCC has updated the CCC-852 LIP Application to separate the “Notice of Loss” from the “Application for Payment” to be consistent with other CCC disaster programs and to align with policy and software development. The revised Application for Payment allows producers to document an alternative market price specific to their operation for eligible livestock losses, including unborn livestock, which will use the alternative market price for the lowest weight category within the applicable livestock category.</P>
                <P>Acceptable documentation for an alternative market price includes, but is not limited to, a producer's verifiable third-party sales or marketing document for their operation. The documentation must include the producer's name as the seller; the buyer's name and contact information; the date and location of the sales transaction; the number of livestock marketed by kind, type, and weight; and the sales price received per head. Alternative pricing must be supported by producer-specific market data for the applicable livestock kind, type, and weight class in the applicable program year.</P>
                <P>The CCC-852, LIP Notice of Loss and Application for Payment, including all required supporting documentation and any alternative price documentation, must be submitted by the program deadline of March 1 following the calendar year in which the loss occurred.</P>
                <HD SOURCE="HD3">4. Other Changes</HD>
                <P>CCC is updating and adding definitions in § 1416.302 for clarity. In addition to updates to the definitions of livestock categories to administer assistance for unborn death losses, this rule also specifies in the definitions of adult and non-adult “caribou” that reindeer and caribou are synonymous, as they are the same species (Rangifer tarandus). It also adds definitions for the categories of water buffalo that are separate from the categories for buffalo; previously, water buffalo were included under “buffalo” for LFP, and this change is intended to reduce confusion. In addition, the rule adds definitions for “program year,” which for LIP means the calendar year, and for “reliable record or documentation” and “verifiable record or documentation” to align with other CCC and FSA disaster programs. This rule also amends § 1416.305 to remove a reference to prior program years in paragraph (c), correct a typographical error in paragraph (d)(8), and clarify that paragraph (g) applies to eligible diseases. It also updates cross-references in § 1416.306.</P>
                <HD SOURCE="HD2">D. TAP</HD>
                <P>TAP provides assistance to eligible orchardists and nursery tree growers (collectively referred to as “producers”) to replant or rehabilitate trees, bushes, and vines that were lost because of an eligible natural disaster. To receive TAP assistance, a producer must first suffer a qualifying tree, bush, or vine mortality loss in the calendar year (or loss period in the case of plant disease); once that threshold is met, the producer may receive assistance for both loss and damage of eligible trees, bushes, and vines. Prior to OBBBA, a producer had to suffer a minimum 15 percent loss, adjusted for normal mortality, in the calendar year (or loss period in the case of plant disease) to be eligible for TAP payments. OBBBA lowered the loss threshold so that a producer qualifies for TAP if they exceed the normal mortality for a tree, bush, or vine, and this rule amends §§ 1416.403(a) and 1416.406(b) to be consistent with that change.</P>
                <P>Additionally, OBBBA increases the portion of a producer's lost or damaged trees, bushes, or vines for which they may receive assistance. This rule amends § 1416.400(b) and § 1416.406(a) to provide that payments will be calculated for the cost of replanting or rehabilitating trees, bushes, or vines that were damaged or lost due to a natural disaster, in excess of normal damage or normal mortality, consistent with OBBBA. Previously, payments were calculated based on the trees, bushes, or vines in excess of 15 percent damage or mortality, adjusted for normal damage or mortality.</P>
                <P>To illustrate these changes, suppose a producer has a stand of 1,000 citrus trees and normal mortality for the stand is 3 percent. The producer lost 200 citrus trees due to an eligible natural disaster. Prior to OBBBA implementation, the producer would have had to lose more than 180 trees in the stand (18 percent of the trees, which represents the 15 percent statutory threshold plus 3 percent normal mortality) to be eligible for TAP. With the OBBBA change, the producer is eligible for a TAP payment if they lose more than 30 trees, which represents 3 percent normal mortality.</P>
                <P>Prior to OBBBA implementation, the producer would have been eligible for reimbursement for replanting costs for 164 of the 200 citrus trees lost. To calculate this number, the number of trees lost (200 trees) was multiplied by 18 percent (15 percent threshold plus 3 percent normal mortality), which equals 36 trees. That number was then subtracted from the total trees lost (200 − 36 = 164). With the change in this rule, the number of trees lost (200 trees) is multiplied by 3 percent normal mortality, which equals 6 trees, and that number is subtracted from the total trees lost, resulting in 194 trees for which the producer would be eligible for payment.</P>
                <P>This rule also increases the reimbursement percentage from 50 percent to 65 percent for the cost of pruning, removal, and other costs to salvage existing trees, bushes, or vines, or, in the case of mortality, to prepare the land for replanting, as mandated by OBBBA (§ 1416.406(a)(2)(i)). The reimbursement amount of 65 percent for replanting costs is not changing, and beginning and veteran farmers and ranchers, as defined in § 718.2, are still eligible for an increased reimbursement amount of 75 percent for both categories of expenses.</P>
                <P>The regulatory amendments to implement OBBBA provisions will be effective for the 2026 and subsequent program years, including for any losses in the 2026 program year that occurred prior to the publication of this rule.</P>
                <P>In addition to the OBBBA changes, CCC is also amending § 1416.407(a) to extend the time for participants to execute required documents and complete TAP practices from 12 months to 24 months after the application is approved, and to allow CCC to grant an extension of up to 36 months when delays are due to circumstances beyond a participant's control. These changes are intended to allow CCC to address situations where participants need additional time for reasons such as backorders or cancellations of orders of replacement trees, which often occur when suppliers are also affected by disaster events. This rule also removes unnecessary provisions in §§ 1416.400(c) and 1416.403(a) related to the loss threshold for pecan tree losses for the 2017 and 2018 calendar years.</P>
                <HD SOURCE="HD1">III. Marketing Assistance Loans and Loan Deficiency Payments</HD>
                <P>
                    Producers of eligible commodities may apply for MALs or LDPs, subject to requirements codified at 7 U.S.C. 9031 and 7 CFR part 1421. MALs are loans that typically mature within 9 months with the commodity pledged as collateral. Alternatively, a producer eligible for an MAL may elect to receive an LDP instead when the alternative repayment rate for the commodity falls below the loan rate, without requiring the commodity to be pledged as collateral.
                    <PRTPAGE P="42320"/>
                </P>
                <P>Section 10309 of OBBBA increased loan rates for crop years 2026 through 2031 for all commodities eligible under the MAL and LDP programs but did not otherwise change the structure of the MAL and LDP programs. Commodities included in these programs include wheat, feed grains, soybeans and other oilseeds, peanuts, pulse crops, rice, cotton, honey, wool (including unshorn pelts), and mohair.</P>
                <P>MALs and LDPs are available beginning with harvest or shearing season for each commodity and extend through the remainder of that commodity's crop year. Nearly all MALs are nonrecourse, meaning that the commodity is used as collateral and may be delivered at maturity as full repayment of the loan. Recourse loans are available for a few commodities that are low quality, contaminated, or for which long term storage is not readily available, meaning that the collateral cannot be delivered as full repayment of the loan. MALs and LDPs must be requested on or before the final loan availability date for the commodity.</P>
                <P>Producers may repay the MAL at a rate that is the lesser of the loan rate plus interest or at a repayment rate announced by USDA. The repayment rate is based on average market prices for the preceding 30 days or an alternative rate set by USDA. If the repayment rate is below the loan rate for that commodity, producers can redeem an MAL at the repayment rate and receive the financial benefit of the difference between the loan rate and the repayment rate, referred to as a marketing loan gain. Hence, MALs act as a price floor. This price floor ensures that producers have a guaranteed minimum price for their commodity and helps stabilize producer incomes during periods of low market prices.</P>
                <P>As an alternative to taking an MAL, a producer may choose to receive an LDP on their crop, provided an LDP is available for the commodity, and the producer is eligible for an MAL. LDPs provide a payment when the repayment rate for a commodity is lower than its loan rate.</P>
                <P>This rule makes technical revisions to the MAL program at 7 CFR part 1421. These revisions include clarification of the role of the Agricultural Marketing Service (AMS) in CCC activities involving Electronic Warehouse Receipts (EWR). Historically, this functionality fell under FSA until Commodity Operations roles moved to AMS in 2018. References to Grain Inspection, Packers and Stockyards Administration (GIPSA) functions were also updated to be functions of AMS. References at 7 CFR part 1421 to Designated Marketing Association (DMA) drawdown accounts for peanuts have been removed because the process to transfer loan or LDP funds to alternative delivery partners, as necessary for disbursement to producers, has been enhanced by using a direct wire process offered by the Federal Reserve Banks known as Fedwire. Parts 1421 and 1427 are amended to make clear that price support provided to producers is limited to commodities produced in the United States. Other technical corrections add clarity to the regulations.</P>
                <HD SOURCE="HD2">A. Honey Nonrecourse Loans</HD>
                <P>Section 10309(b) of OBBBA extends the honey MAL and LDP programs from crop years 2026 through 2031 and increases the honey loan rate. This rule also makes minor technical corrections to the honey regulations in 7 CFR part 1434.</P>
                <HD SOURCE="HD2">B. Upland and ELS Cotton</HD>
                <P>
                    This rule updates 7 CFR part 1427 to reflect OBBBA changes for the 2026 through 2031 crop years, including higher storage rates for upland and ELS cotton, a revised formula for the prevailing world market price for upland cotton to include the 3 lowest-price quotes (rather than the use of 5 lowest-priced quotes), introduction of a prevailing world market price and adjusted world price for ELS cotton, and a formula to determine a refund amount for upland cotton loan redemptions when the adjusted world price (AWP) 
                    <SU>2</SU>
                    <FTREF/>
                     declines within 30-days of the loan repayment date. This rule also makes technical clarifying changes and removes expired provisions.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The upland cotton Adjusted World Price (AWP) is the upland cotton prevailing world market price (also referred to as the “Far East price” (FE)), adjusted for location (reflected in the cost to market) and quality, and may be further adjusted in accordance with 7 CFR 1427.25. The AWP is also referred to as the repayment rate.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">1. Payment of Cotton Storage Costs</HD>
                <P>USDA does not pay for storage on non-forfeited commodities; however, for cotton, USDA credits storage (up to the maximum storage credit rate) toward the loan at redemption when the loan rate plus interest plus storage exceeds the AWP. Depending on the AWP, this can result in a partial or full storage credit. Storage payment rates are calculated as the lower of the current marketing year warehouse storage charge or the area-specific storage payment rate cap. Section 10309 of OBBBA (7 U.S.C. 9034(g)) increases storage payment rates compared to previous levels established by CCC in 2006. Effective with the 2026 cotton crop, these storage payment rates are capped at $4.90 for locations in California and Arizona, and at $3.00 for all other states. Additionally effective with the 2026 cotton crop, OBBBA eliminates the prior percentage-based reduction of 10 percent of the storage payment rate cap that was included in section 1204 of the Agricultural Act of 2014 (7 U.S.C. 9034(g)).</P>
                <HD SOURCE="HD3">2. Upland Cotton Prevailing World Market Price Change</HD>
                <P>Historically, the prevailing world market price for upland cotton, referred to as the “Far East price” (FE), was based on the average of the quotations from the preceding Friday through Thursday for the 5 lowest-priced growths of Middling one and three-thirty-second inch (M 1 3/32 inch) cotton, CFR (cost and freight) Far East. Section 10310 of OBBBA changed the prevailing world market price for upland cotton to be based on the 3 lowest-priced growth quotes, effective retroactively starting from the date of OBBBA's enactment on July 4, 2025. As has been the case historically, the world market price for upland cotton, which is a benchmark for global upland cotton prices, is adjusted for quality and the estimated cost to market for U.S. producers to calculate the upland cotton AWP (repayment rate).</P>
                <HD SOURCE="HD3">3. ELS Prevailing World Market Price Calculation</HD>
                <P>Historically, ELS cotton was redeemed at the loan rate plus interest with no alternative repayment rate, and a prevailing world market price and adjusted world price were not calculated. Section 10310 of OBBBA (7 U.S.C. 9034) provides that a prevailing world market price will be calculated and announced weekly in a manner similar to the process for upland cotton—using the 3 lowest-priced growth quotes adjusted for quality. The prevailing world market price (“extra long staple Far East price” or ELSFE), regardless of whether or not a quality adjustment is made, will then be adjusted for the U.S. producers' average cost to market to calculate the ELS cotton AWP used for repayments.</P>
                <HD SOURCE="HD3">4. 30-Day Loan Optimization Window (LOW) for Upland Cotton</HD>
                <P>
                    Upland cotton redemptions are to be made at the lesser of the loan rate, plus interest and other charges, or the AWP (repayment rate) as announced by CCC at 4 p.m. Eastern time each Thursday. Section 10310 of OBBBA, which amends section 1204(b) of the Agricultural Act of 2014, states that in 
                    <PRTPAGE P="42321"/>
                    the event that a lower AWP is announced within the 30 calendar days immediately following the date of loan repayment, FSA will issue a refund to the producer equal to the difference between the lowest AWP during the 30-day period and the AWP in effect on the date of loan repayment. The term “producer” includes the remitter or redeemer of the marketing assistance loan. This provision ensures that if market prices drop shortly after repayment, the producer benefits from the lower price through a refund. If a producer requests an LDP in lieu of an MAL, and a lower AWP is announced during the 30-day period immediately following the request, the producer will receive an additional LDP disbursement. The additional LDP disbursement will be equal to the difference in the LDP rate used in the producer's initial LDP request and the lowest AWP during the 30-day period. The term “producer” in this case, will be the requestor of the initial LDP. Producers who elect to receive an LDP in lieu of an MAL cannot pledge the same cotton as collateral under the MAL program and therefore any LDP recipients forfeit any storage credits or other benefits associated with MAL participation.
                    <SU>3</SU>
                    <FTREF/>
                     A recalculated rate may not, under any circumstances, result in an LDP for which the producer has not already submitted an approved application. This rule amends §§ 1427.19 and 1427.23.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         MAL provides producers with short-term operating capital, while the LDP is a one-time payment option chosen in place of the loan and any benefits that would accrue under MAL provisions.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">5. Additional Changes for Cotton</HD>
                <P>In addition to implementing OBBBA changes, FSA is making some technical changes for clarity and consistency within the regulations.</P>
                <P>This rule amends § 1427.3 to remove the definition for “cotton commercial bank” and to clarify the definitions of “upland cotton” and “ELS cotton.” ELS cotton is cotton of the Gossypium barbadense variety or any hybrid where the barbadense variety predominates. Upland cotton is any strain of the Gossypium variety or a variety that does not include the barbadense species.</P>
                <P>Section 1427.22 is updated to include the availability of Commodity Certificate Exchanges (CCE) for ELS cotton on or before loan maturity. Under this rule, CCEs will allow a producer to redeem collateral at the prevailing world market price using a certificate exchange process that provides a market loan gain that is not subject to payment limits and AGI provisions.</P>
                <P>This rule also makes technical corrections to §§ 1427.6, 1427.19, and 1427.23. References to “cotton commercial bank” are removed and contact information is provided for AMS's Warehouse and Commodity Management Division. References to the tariff storage rate for warehouse storage for cotton crops under loan are updated to reflect the current marketing year. The term “upland” is removed where it applies to both upland and ELS cotton. With the introduction of the ELS cotton AWP (repayment rate), storage credit applied to loan repayments when the adjusted world market price is less than the combined value of loan principal, accrued interest, and warehouse storage, are now applicable to both upland and ELS cotton.</P>
                <HD SOURCE="HD2">C. Sugar Program</HD>
                <P>This rule amends the Sugar Program regulations in 7 CFR part 1435 to implement the changes in section 10312(a) of OBBBA (42 U.S.C. 7272), which extends the Sugar Program from crop year 2025 to 2031 and increased raw cane and refined beet sugar loan rates (§ 1435.101(a) and (b)). Section 10312(b)(1)(a) of OBBBA (7 U.S.C. 7287) also requires the CCC to establish storage rates for forfeited sugar in amounts not less than newly established rates (§ 1435.105(j)).</P>
                <P>OBBBA added an exception to certain procedures that apply when reassigning beet sugar allocations following an upward adjustment in the Overall Allotment Quantity (§ 1435.303(d)). If an upward adjustment in sugar marketing allotments was made at the beginning of the fiscal year, each processor's allocation will be increased by the same percentage that the allotment increased. Section 10312(c)(2) of OBBBA (7 U.S.C. 1359cc(g)(2)) added an exception such that when adjusting beet sugar allocations priority will be given to beet sugar processors with available sugar (§ 1435.303(d)). Section 10312(c)(3) of OBBBA (7 U.S.C. 1359ee(b)(2)) also provides consistency for beet sugar processors who will need additional allocations to market their sugar supplies. Under the requirements established by OBBBA, the first reassignment of sugar marketing allocations now must be published no later than 30 days after the publication of each January's World Supply and Demand Estimates report (§ 1435.309(d)(5)).</P>
                <P>This rule also makes technical corrections to other sugar provisions, such as clarifying that FSA, Farm Production and Conservation (FPAC), and AMS will administer the Sugar Program for the CCC (§ 1435.1(a)). This rule specifies that sugar pledged as collateral during the crop year may not be pledged as collateral in a subsequent crop year (§ 1435.102(c)(6)). Additionally, this rule provides the rates of storage to be used for crop years 2012 through 2024 that were inadvertently omitted from 7 CFR part 1435 (§ 1435.105(j)).</P>
                <P>This rule also updates definitions related to sugar. Section 1435.2 adds a definition for the domestic sugar industry. Three definitional changes are made in § 1435.2: (1) the definition of “crop year” is updated to clarify that a crop year relates to the year in which harvest and processing of the crop begins; (2) clarifying language is added to the definition of “imports” to provide the same level of specificity used in USDA's survey for importers; and (3) a definition of “new entrant” is added because §§ 1435.305, 1435.306, and 1435.308 all relate to new entrant provisions, yet the term had not yet been defined. In addition, § 1435.200h(i) is amended to reflect specific audit terms that have been adopted over time. USDA found that the previous terms were too rigid for sugar industry reporters (who are required to report data monthly to USDA) to manage without incurring burdensome costs.</P>
                <HD SOURCE="HD2">D. Feedstock Flexibility Program</HD>
                <P>Although the Feedstock Flexibility Program (FFP) was not mentioned in OBBBA, this rule also updates the regulations in Subpart G to extend FFP through crop year 2026 as authorized in the Continuing Appropriations, Agriculture, Legislative Branch, Military Construction and Veterans Affairs, and Extensions Act, 2026 (Pub. L. 119-37). FFP provides an alternative for USDA to dispose of sugar when the marketplace is oversupplied.</P>
                <HD SOURCE="HD1">VI. ARC and PLC Correction</HD>
                <P>
                    On January 12, 2026, CCC published a final rule amending the regulations for the ARC and PLC programs to conform to OBBBA provisions and make minor administrative changes and updates (91 FR 1043). In that rule, CCC revised the definition of “historically irrigated percentage” in § 1412.3 to update the applicable years; however, CCC inadvertently omitted an update to reflect that it will be calculated using both the planted and considered planted (P&amp;CP) acreage of the commodity plus subsequently planted acreage of the commodity. Use of both P&amp;CP and subsequently planted crop acreage provides a more accurate reflection of a farm's historical irrigation of a commodity. This rule also corrects a typographical error in the applicable 
                    <PRTPAGE P="42322"/>
                    beginning year in paragraph (1) of the definition of “reference price” in § 1412.3. As specified in section 10301(b) of OBBBA, the references prices in paragraph (1) are effective beginning with the 2025 crop year.
                </P>
                <HD SOURCE="HD1">V. DMC Correction</HD>
                <P>On January 12, 2026, CCC published a final rule amending the regulations for the DMC Program to conform to OBBBA provisions and make minor administrative changes and updates (91 FR 1043). In that rule, CCC revised § 1430.407(i) but it contained an erroneous cross-reference. That error is corrected in this rule.</P>
                <HD SOURCE="HD1">VI. Severability</HD>
                <P>The modifications to ARC, PLC, DMC, ELAP, LFP, LIP, TAP, MAL, LDP, and the Sugar Program authorized by OBBBA are distinct and severable from one another, as well as from the minor administrative changes and updates to the regulations. Each provision is designed to function independently, ensuring that the rule as a whole remains effective and aligned with the agency's intent, even if certain provisions were to be invalidated.</P>
                <HD SOURCE="HD1">VII. Regulatory Analyses</HD>
                <HD SOURCE="HD2">A. Effective Date, Notice and Comment, and Paperwork Reduction Act</HD>
                <P>As specified in 7 U.S.C. 9091(c)(2), the regulations to implement ARC, PLC, DMC, ELAP, LFP, LIP, TAP, MAL, LDP, and the Sugar Program are exempt from:</P>
                <P>• The Paperwork Reduction Act (44 U.S.C. chapter 35), and</P>
                <P>• The notice and comment provisions of 5 U.S.C. 553.</P>
                <FP>Further, the Administrative Procedure Act (APA, 5 U.S.C. 553(a)(2)) provides that the provisions requiring notice and comment and a 30-day delay in the effective date do not apply when the rule involves specified actions, including matters relating to benefits or contracts. This rule governs payments to agricultural producers and therefore falls within the benefits exemption.</FP>
                <P>
                    The Office of Information and Regulatory Affairs has found that this rule meets the criteria at 5 U.S.C. 804(2) of the Congressional Review Act (CRA). Ordinarily, such a finding would necessitate delaying its effective date for 60 days (5 U.S.C. 801(a)(3)(A)). However, 7 U.S.C. 9091(c)(3) directs the Secretary to use the authority provided by the CRA at 5 U.S.C. 808(2), which allows an agency to make such regulations effective immediately with good cause. USDA has determined that such good cause exists. For the reasons noted above—the APA exception at 7 U.S.C. 9091(c)(2)(B) and the applicability of 5 U.S.C. 553(a)(2)—such notice and public procedure are unnecessary for this rule. Further, this rule implements mandatory requirements of the OBBBA, and the assistance provided by this rule is necessary to help beneficiaries sustain their normal business operations. As a result, USDA finds that notice and public procedure are contrary to the public interest. Therefore, USDA is not required to delay the effective date for 60 days from the date of publication. Accordingly, this rule is effective upon publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>This rule is exempt from the regulatory analysis requirements of the Regulatory Flexibility Act (5 U.S.C. 601-612), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA) because it involves matters relating to benefits. The requirements for the regulatory flexibility analysis in 5 U.S.C. 603 and 604 are specifically tied to the requirement for a proposed rule by section 553 or any other law; in addition, the definition of rule in 5 U.S.C. 601 is tied to the publication of a proposed rule.</P>
                <HD SOURCE="HD2">B. Executive Orders 12866, 13563, and 14192</HD>
                <P>Executive Order 12866, “Regulatory Planning and Review,” and Executive Order 13563, “Improving Regulation and Regulatory Review,” direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). Executive Order 13563 emphasized the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. Executive Order 14192, “Unleashing Prosperity Through Deregulation,” announced the Administration policy to significantly reduce the private expenditures required to comply with Federal regulations to secure America's economic prosperity and national security and the highest possible quality of life for each citizen and to alleviate unnecessary regulatory burdens placed on the American people. In line with the Executive order requirements, the Agency chose this regulatory approach, which implements mandatory provisions of the OBBBA and clarifies and simplifies program requirements, to maximize benefits and minimize burden on American producers. This rule is not an Executive Order 14192 regulatory action because it does not impose any more than de minimis regulatory costs.</P>
                <P>
                    The Office of Management and Budget (OMB) designated this rule as economically significant under Executive Order 12866, section 3(f)(1), and therefore, OMB has reviewed this rule. The costs and benefits of this rule are summarized below. The full CBA is available on 
                    <E T="03">regulations.gov.</E>
                </P>
                <HD SOURCE="HD2">C. Cost Benefit Analysis Summary</HD>
                <P>The program changes in this rule are, except in the case of MALs and LDPs, largely independent of one another and, generally, affect payment parameters or expand the situations that are now eligible for payment.</P>
                <P>
                    • 
                    <E T="03">Supplemental Disaster Assistance</E>
                    —CCC is making numerous changes to the supplemental disaster assistance programs, which encompass ELAP, LFP, LIP, and TAP. Examples of OBBBA-driven changes include setting a fixed mortality rate for honeybees for ELAP and increasing the timeliness and amount of LFP payments. By far, the largest increase in projected outlays within this category is due to the LFP changes, which are estimated at $343 million annually. For the other disaster programs combined, the annual increase is $39 million, bringing the total for this category to $382 million annually.
                </P>
                <P>
                    • 
                    <E T="03">MALs and LDPs</E>
                    —The major driver increasing MALs and LDPs is the OBBBA increase in marketing assistance loan rates. In addition, OBBBA mandates certain changes to the cotton and sugar programs. The intertwined nature of the OBBBA changes (including for cotton and sugar) is analyzed in a composite fashion and the aggregate estimate (taking into account the intertwined nature of the changes) results in a projected outlay increase of $545 million annually. The cotton and sugar changes are embedded within this estimate.
                </P>
                <P>The total cost of these changes is estimated at $927 million ($382 million + $545 million) annually.</P>
                <HD SOURCE="HD2">D. Environmental Review</HD>
                <P>The environmental impacts have been considered in a manner consistent with the provisions of the National Environmental Policy Act (NEPA, 42 U.S.C. 4321-4347) and the USDA regulation for compliance with NEPA (7 CFR part 1b).</P>
                <P>
                    This rule implements primarily mandatory changes to the ELAP, LFP, LIP, TAP, MAL, LDP, and Sugar Program provisions that are required by the OBBBA, with limited discretionary aspects that do not have the potential to impact the human environment as they are administrative. Accordingly, these 
                    <PRTPAGE P="42323"/>
                    discretionary aspects are covered by the FSA Categorical Exclusions specified in 7 CFR 1b.4(c)(16)(ix) that applies to safety net programs and § 1b.(c)(16)(vii) that applies to price support programs.
                </P>
                <P>No Extraordinary Circumstances (§  1b.3(f)) exist because these are administrative payment programs. As such, the implementation of and participation in the ELAP, LFP, LIP, TAP, MAL, LDP, and Sugar Program do not constitute major Federal actions that would significantly affect the quality of the human environment, individually or cumulatively. Therefore, FSA will not prepare an environmental assessment or environmental impact statement for this action and, consistent with §  1b.3(g), this document serves as the programmatic finding of applicability and no extraordinary circumstance (FANEC) for this Federal action.</P>
                <HD SOURCE="HD2">E. Executive Order 13175</HD>
                <P>This rule has been reviewed in accordance with the requirements of Executive Order 13175, “Consultation and Coordination with Indian Tribal Governments.” Executive Order 13175 requires Federal agencies to consult and coordinate with Tribes on a Government-to-Government basis on policies that have Tribal implications, including regulations, legislative comments or proposed legislation, and other policy statements or actions that have substantial direct effects on one or more Indian Tribes, on the relationship between the Federal Government and Indian Tribes, or on the distribution of power and responsibilities between the Federal Government and Indian Tribes.</P>
                <P>USDA has assessed the impact of this rule on Indian Tribes and determined that this rule does not, to our knowledge, have Tribal implications that required Tribal consultation at this time. If a Tribe requests consultation, the USDA Farm Service Agency will work with the FSA Federal Preservation Officer, who will engage the Office of Tribal Relations as needed, to ensure meaningful consultation is provided.</P>
                <HD SOURCE="HD2">F. Unfunded Mandates Reform Act</HD>
                <P>Title II of the Unfunded Mandates Reform Act of 1995 (UMRA, Pub. L. 104-4) requires Federal agencies to assess the effects of their regulatory actions on State, local, and Tribal governments, or the private sector. Agencies generally must prepare a written statement, including cost benefit analysis, for proposed and final rules with Federal mandates that may result in expenditures of $100 million or more in any 1 year for State, local, or Tribal governments, in the aggregate, or to the private sector. UMRA generally requires agencies to consider alternatives and adopt the more cost effective or least burdensome alternative that achieves the objectives of the rule. This rule contains no Federal mandates, as defined in Title II of UMRA, for State, local, and Tribal governments or the private sector. Therefore, this rule is not subject to the requirements of sections 202 and 205 of UMRA.</P>
                <HD SOURCE="HD2">G. E-Government Act Compliance</HD>
                <P>FSA is committed to complying with the E-Government Act of 2002, to promote the use of the internet and other information technologies to provide increased opportunities for citizen access to Government information and services, and for other purposes.</P>
                <HD SOURCE="HD3">Federal Assistance Programs</HD>
                <P>The titles and numbers of the Federal assistance programs, as found in the Assistance Listing, to which this document applies are 10.112—Price Loss Coverage, 10.113—Agriculture Risk Coverage, 10.127—Dairy Margin Coverage, 10.051—Commodity Loans and Loan Deficiency Payments, 10.088—Livestock Indemnity Program, 10.089—Livestock Forage Disaster Program, 10.091—Emergency Assistance for Livestock, Honeybees, and Farm-Raised Fish Program, and 10.092—Tree Assistance Program.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>7 CFR Part 1412</CFR>
                    <P>Acreage allotments, Cotton, Feed grains, Oilseeds, Peanuts, Price support programs, Reporting and recordkeeping requirements, Rice, Soil conservation, Wheat.</P>
                    <CFR>7 CFR Part 1416</CFR>
                    <P>Administrative practice and procedure, Agriculture, Bees, Dairy products, Disaster assistance, Fruits, Livestock, Nursery stock, Reporting and recordkeeping requirements, Seafood.</P>
                    <CFR>7 CFR Part 1421</CFR>
                    <P>Barley, Feed grains, Grains, Loan programs—agriculture, Oats, Oilseeds, Peanuts, Price support programs, Reporting and recordkeeping requirements, Soybeans, Surety bonds, Warehouses, Wheat.</P>
                    <CFR>7 CFR Part 1427</CFR>
                    <P>Cotton, Cottonseeds, Loan programs—agriculture, Packaging and containers, Price support programs, Reporting and recordkeeping requirements, Surety bonds, Warehouses.</P>
                    <CFR>7 CFR Part 1430</CFR>
                    <P>Dairy products, Fraud, Penalties, Price support programs, Reporting and recordkeeping requirements.</P>
                    <CFR>7 CFR Part 1434</CFR>
                    <P>Honey, Loan programs—agriculture, Price support programs, Reporting and recordkeeping requirements.</P>
                    <CFR>7 CFR Part 1435</CFR>
                    <P>Loan programs—agriculture, Marketing quotas, Penalties, Price support programs, Reporting and recordkeeping requirements, Sugar.</P>
                </LSTSUB>
                <P>For the reasons discussed above, CCC amends the regulations in 7 CFR parts 1412, 1416, 1421, 1427, 1430, 1434, and 1435 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1412—AGRICULTURE RISK COVERAGE AND PRICE LOSS COVERAGE</HD>
                </PART>
                <REGTEXT TITLE="7" PART="1412">
                    <AMDPAR>1. The authority citation for part 1412 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 7 U.S.C. 1508b, 7911-7912, 7916, 8702, 8711-8712, 8751-8752, 9011-9018, and 15 U.S.C. 714b and 714c.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1412">
                    <AMDPAR>2. Amend § 1412.3 as follows:</AMDPAR>
                    <AMDPAR>a. Revise the definition of “Historical irrigated percentage”; and</AMDPAR>
                    <AMDPAR>b. In the definition of “Reference price”, in paragraph (1) introductory text, remove “2026” and add “2025” in its place.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1412.3 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Historical irrigated percentage</E>
                             means the percentage of the covered commodity on a farm that was irrigated, including both P&amp;CP and subsequently planted crop acreage, divided by the total acreage of the P&amp;CP and subsequently planted covered commodity between the years 2019 through 2023 on the farm.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 1416—EMERGENCY AGRICULTURAL DISASTER ASSISTANCE PROGRAMS</HD>
                </PART>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>3. The authority citation for part 1416 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>7 U.S.C. 9081 and 15 U.S.C. 714b and 714c.</P>
                    </AUTH>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart A—General Provisions for Supplemental Agricultural Disaster Assistance Programs</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>4. Amend §  1416.2 as follows:</AMDPAR>
                    <AMDPAR>a. Revise paragraphs (a), (b), and (d); and</AMDPAR>
                    <AMDPAR>b. Remove and reserve paragraph (e).</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <PRTPAGE P="42324"/>
                        <SECTNO>§ 1416.2 </SECTNO>
                        <SUBJECT> Administration of ELAP, LFP, LIP, and TAP.</SUBJECT>
                        <P>(a) The programs in subparts B through E of this part will be administered under the general supervision and direction of the Executive Vice President, CCC, and will be carried out in the field by FSA State and county committees, respectively.</P>
                        <P>(b) State and county committees, and representatives and their employees, do not have authority to modify or waive any of the provisions of the regulations set forth in this part.</P>
                        <STARS/>
                        <P>(d) No provision or delegation to an FSA State or county committee will preclude the Executive Vice President, CCC, or a designee, from determining any question arising under this part, or from reversing or modifying any determination made by an FSA State or county committee.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>5. Amend § 1416.6 by revising paragraphs (a) and (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1416.6 </SECTNO>
                        <SUBJECT> Payment eligibility and limitation.</SUBJECT>
                        <P>(a) Payment limitation will apply to LFP in accordance with part 1400 of this chapter.</P>
                        <STARS/>
                        <P>(c) LIP, LFP, ELAP, and TAP will be administered in accordance with the average adjusted gross income (AGI) limitation provisions in part 1400 of this chapter.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1416.7 </SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>6. Amend § 1416.7 in paragraph (a) by removing “part 1403 of this chapter” and adding “part 3 of this title” in its place.</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1416.9 </SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>7. Amend § 1416.9 in paragraph (a) by removing “part 1403 of this chapter” and adding “part 3 of this title” in its place.</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1416.11 </SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>8. Amend § 1416.11 in paragraph (a) by removing “part 1403 of this chapter” and adding “part 3 of this title” in its place.</AMDPAR>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart B—Emergency Assistance for Livestock, Honeybees, and Farm-Raised Fish Program</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>9. Amend § 1416.102 as follows:</AMDPAR>
                    <AMDPAR>a. Add the definitions of “Adult water buffalo bull”, “Adult water buffalo cow”, and “Bird depredation” in alphabetical order;</AMDPAR>
                    <AMDPAR>b. In the definition of “Eligible loss condition”, remove the words “and colony collapse disorder” and add “colony collapse disorder, and bird depredation” in their place;</AMDPAR>
                    <AMDPAR>c. Revise the definition of “Farm-raised fish”;</AMDPAR>
                    <AMDPAR>d. Add the definitions of “Freshwater”, “Harvested feed or feedstuffs”, “Miles above normal”, and “Non-adult water buffalo” in alphabetical order;</AMDPAR>
                    <AMDPAR>e. Revise the definition of “Program year”; and</AMDPAR>
                    <AMDPAR>f. Add the definition of “Truckload” in alphabetical order.</AMDPAR>
                    <P>The additions and revision read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.102 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Adult water buffalo bull</E>
                             means a male animal of that breed that was used for breeding purposes and was at least 2 years old before the beginning date of the eligible adverse weather or eligible loss condition.
                        </P>
                        <P>
                            <E T="03">Adult water buffalo cow</E>
                             means a female animal of that breed that had delivered one or more offspring before the beginning date of the eligible adverse weather or eligible loss condition. A first-time bred water buffalo heifer is also considered an adult water buffalo cow if it was pregnant by the beginning date of the eligible adverse weather or eligible loss condition.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Bird depredation</E>
                             means damage or loss caused by piscivorous birds, to freshwater farm-raised fish.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Farm-raised fish</E>
                             means:
                        </P>
                        <P>(1) For losses other than losses due to bird depredation, any aquatic species that is propagated and reared in a controlled environment; and</P>
                        <P>(2) For losses due to bird depredation, fish propagated and reared in a controlled freshwater environment, excluding crayfish and crawfish.</P>
                        <P>
                            <E T="03">Freshwater</E>
                             means water that is low in salinity with dissolved salt concentrations of less than 0.5 parts per thousand and suitable for species that thrive outside marine environments.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Harvested feed or feedstuffs</E>
                             means, for the purpose of purchased or produced feed under ELAP, feed or feedstuffs that are mechanically harvested in the field, and wrapped, twined, stacked, or combined in a manner that the harvested product can be transported from one area to another. It does not include material left in a windrow or as straw in the field.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Miles above normal</E>
                             means mileage from a single trip from 1 point to another, and not multiple stops or end points, and it does not include mileage for delivery that is not identified clearly by mileage rate on verifiable documentation.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Non-adult water buffalo</E>
                             means a weaned animal of that breed that on or before the beginning date of the eligible adverse weather or loss condition does not meet the definition of adult water buffalo cow or bull in this section.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Program year</E>
                             means the calendar year, January 1 through December 31.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Truckload</E>
                             means, for transportation of livestock, feed, or feedstuff, a load that:
                        </P>
                        <P>(1) Is transported by a motorized land vehicle that is clearly intended for operation on highways, and is either owned by the producer or for which the producer directly pays for the transportation of livestock, feed, or feedstuffs based on a rate per loaded mile from the distribution point to the first delivery location;</P>
                        <P>(2) Is considered a single trip and only includes mileage from distribution point to the producer's delivery location of the eligible livestock, not multiple end points or more than one stop; and</P>
                        <P>(3) Must include a clearly identified mileage rate on verifiable documentation.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>10. Amend § 1416.103 by adding paragraph (k) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1416.103 </SECTNO>
                        <SUBJECT>Eligible losses, adverse weather, and other loss conditions.</SUBJECT>
                        <STARS/>
                        <P>
                            (k) For losses due to bird depredation, the producer must have propagated or reared eligible farm-raised fish in a controlled environment and have suffered eligible damage or loss due to bird depredation, including costs associated with the deterrence of piscivorous birds, the value of lost fish and revenue due to bird depredation, and costs associated with disease loss from bird depredation. Losses of crawfish, crayfish, saltwater fish, or any other fish not considered freshwater are not eligible. The losses must have been associated with acres of freshwater that were reported to FSA on a timely filed acreage report, as determined by CCC, as water used for propagating and growing eligible freshwater farm-raised fish in a controlled environment and were in use at the time of bird depredation. Unused ponds or waterways, bodies of water not under control of the producer, and any water that is reduced due to drought are not eligible acres for bird depredation 
                            <PRTPAGE P="42325"/>
                            losses. Payments can only be earned once per program year for total eligible acres.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>11. Amend § 1416.104 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (a)(1), add the words “adult or non-adult water buffalo,” after “bison,”;</AMDPAR>
                    <AMDPAR>b. Redesignate paragraphs (b)(5) through (15) and (16) through (18) as paragraphs (b)(6) through (16) and (18) through (20), respectively;</AMDPAR>
                    <AMDPAR>c. Add new paragraphs (b)(5) and (17);</AMDPAR>
                    <AMDPAR>d. In paragraph (c)(6), remove the words “and buffalo or bison and beefalo” and add “buffalo or bison, beefalo, and water buffalo” in their place; and</AMDPAR>
                    <AMDPAR>e. Add paragraph (f)(3).</AMDPAR>
                    <P>The additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.104 </SECTNO>
                        <SUBJECT>Eligible livestock, honeybees, and farm-raised fish.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(5) Adult water buffalo cows or bulls;</P>
                        <STARS/>
                        <P>(17) Non-adult water buffalo;</P>
                        <STARS/>
                        <P>(f) * * *</P>
                        <P>(3) For losses due to bird depredation, the farm-raised fish must:</P>
                        <P>(i) Be propagated or reared in a controlled freshwater environment;</P>
                        <P>(ii) Have been maintained for commercial use as part of the farming operation; and</P>
                        <P>(iii) Have been physically located in the county where the piscivorous birds were present on the beginning day of the loss condition.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>12. Amend § 1416.105 by revising paragraph (d) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1416.105 </SECTNO>
                        <SUBJECT> Eligible producers, owners, and contract growers.</SUBJECT>
                        <STARS/>
                        <P>(d) To be considered an eligible farm-raised fish producer for feed, death, and bird depredation loss purposes, the participant must have produced eligible farm-raised fish, as specified in § 1416.104(f) for commercial use as part of a farming operation and must have had a loss that is determined to be eligible as specified in § 1416.103(i) for feed and death losses or § 1416.103(k) for bird depredation losses.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>13. Amend § 1416.106 as follows:</AMDPAR>
                    <AMDPAR>a. Revise paragraph (a)(2)(ii);</AMDPAR>
                    <AMDPAR>b. Redesignate paragraph (a)(2)(iii) as paragraph (a)(2)(iv);</AMDPAR>
                    <AMDPAR>c. Add new paragraph (a)(2)(iii) and paragraph (g).</AMDPAR>
                    <P>The revision and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.106 </SECTNO>
                        <SUBJECT> Notice of loss and application process.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(2) * * *</P>
                        <P>(ii) For honeybee feed, honeybee colony, and honeybee hive losses a completed Emergency Loss Assistance for Honeybees Application;</P>
                        <P>(iii) For farm-raised fish feed or death losses and damage and loss due to bird depredation, a completed Emergency Loss Assistance for Farm-Raised Fish Application; and</P>
                        <STARS/>
                        <P>(g) For farm-raised fish losses due to bird depredation:</P>
                        <P>(1) A producer must submit by March 1 after the end of the applicable program year:</P>
                        <P>(i) A report indicating acres of ponds in use at the time of bird depredation, updated from the timely filed acreage report per § 1416.107(a)(1); and</P>
                        <P>(ii) An active U.S. Fish and Wildlife Depredation permit with cormorant, American white pelican, heron, or Great egret listed on the permit; and</P>
                        <P>(2) If requested by FSA, a producer must also provide:</P>
                        <P>(i) Documentation to substantiate the producer's use of eligible acres of freshwater reported;</P>
                        <P>(ii) Documentation of the producer's inventory losses; and</P>
                        <P>(iii) A minimum of 3 of the following 5 items:</P>
                        <P>(A) Documentation that losses are from bird depredation, supported by evidence like bird sightings, fish mortality records, Aerial Surveys, or third-party assessments;</P>
                        <P>(B) Documentation of annual expenditures on non-lethal and lethal methods to prevent or reduce bird presence;</P>
                        <P>(C) Documentation of costs attributed to disease spread by birds, such as prescriptions for medicated feed or any other costs showing disease loss from bird depredation;</P>
                        <P>(D) A USDA-Wildlife Services or U.S. Fish and Wildlife Service approved bird harassment plan; and</P>
                        <P>(E) A year-end collection report of the number of birds terminated and reported to the U.S. Fish and Wildlife Service.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>14. Revise § 1416.107 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1416.107 </SECTNO>
                        <SUBJECT> Notice of loss and application period.</SUBJECT>
                        <P>(a) To receive an ELAP payment, the participant must submit:</P>
                        <P>(1) A timely filed acreage report in accordance with §§ 1416.106 and 718.101 through 718.112 of this title; and</P>
                        <P>(2) The following to the FSA county office by March 1 after the end of the applicable program year:</P>
                        <P>(i) A notice of loss;</P>
                        <P>(ii) A complete application for payment; and</P>
                        <P>(iii) Any other documentation required by this subpart.</P>
                        <P>(b) If additional information is requested by FSA to verify the producer's eligibility or losses under this subpart, the producer must submit the requested information by the later of March 1 after the end of the applicable program year or 60 days after the date of the request.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>15. Amend § 1416.109 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), remove “§§ 1416.110 through 1416.112” and add “§§ 1416.110, 1416.111, and 1416.112(a) through (d)” in its place; and</AMDPAR>
                    <AMDPAR>b. Add paragraph (e).</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.109 </SECTNO>
                        <SUBJECT>National payment rate.</SUBJECT>
                        <STARS/>
                        <P>(e) For an eligible farm-raised fish producer for eligible damage and loss due to bird depredation, payments calculated in § 1416.112(c) will be based on a payment rate of not less than $600 per eligible acre of freshwater. For program year 2026, the rate will be $600 for all species of eligible farm-raised fish. For subsequent program years, CCC may increase the payment rate if CCC determines an increase in the payment rate is warranted. When determining the payment rate, CCC will take into account:</P>
                        <P>(1) Costs associated with the deterrence of piscivorous birds;</P>
                        <P>(2) The value of lost fish and revenue due to bird depredation; and</P>
                        <P>(3) Costs associated with disease loss from bird depredation.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>16. Amend § 1416.110 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), add the word “grazing” before the word “days”;</AMDPAR>
                    <AMDPAR>b. Redesignate paragraph (r) as paragraph (s); and</AMDPAR>
                    <AMDPAR>c. Add new paragraph (r).</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.110 </SECTNO>
                        <SUBJECT>Livestock payment calculations.</SUBJECT>
                        <STARS/>
                        <P>
                            (r) For the purpose of payments under paragraph (n) of this section, reimbursable transportation costs for a truckload are limited to mileage of the truckload supported by an established, published hauling rate per loaded mile. Any parcel delivery or distribution-center delivery service including UPS, FedEx, U.S. Postal Service, or similar carriers and any transportation fees or 
                            <PRTPAGE P="42326"/>
                            handling fees applied are not eligible for reimbursement.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>17. Amend § 1416.111 by revising paragraph (b)(2) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1416.111 </SECTNO>
                        <SUBJECT>Honeybee payment calculations.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(2) Number of eligible honeybee colonies that were damaged or destroyed due to an eligible adverse weather or eligible loss condition, in excess of normal honeybee mortality. For 2026 and subsequent program years, normal honeybee mortality is 15 percent.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>18. Amend § 1416.112 as follows:</AMDPAR>
                    <AMDPAR>a. Redesignate paragraph (c) as paragraph (d); and</AMDPAR>
                    <AMDPAR>b. Add new paragraph (c).</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.112 </SECTNO>
                        <SUBJECT>Farm-raised fish payment calculations.</SUBJECT>
                        <STARS/>
                        <P>(c) An eligible producer of freshwater farm-raised fish may receive payments for eligible damage and loss due to bird depredation, as specified in § 1416.103(k), based on the payment rate determined in accordance with § 1416.109(e), multiplied by 85 percent of the total eligible acres of freshwater in production for the program year, as provided in 1416.103(k).</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart C—Livestock Forage Disaster Program</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>19. Amend § 1416.202 by adding the definitions of “Adult water buffalo bull”, “Adult water buffalo cow”, and “Non-adult water buffalo” in alphabetical order to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1416.202 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Adult water buffalo bull</E>
                             means a male animal of that breed that was used for breeding purposes and was at least 2 years old before the beginning date of the qualifying drought or fire.
                        </P>
                        <P>
                            <E T="03">Adult water buffalo cow</E>
                             means a female animal of that breed that had delivered one or more offspring before the beginning date of the qualifying drought or fire. A first-time bred water buffalo heifer is also considered an adult water buffalo cow if it was pregnant by the beginning date of the qualifying drought or fire.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Non-adult water buffalo</E>
                             means a weaned animal of that breed that on or before the beginning date of the qualifying drought or fire does not meet the definition of adult water buffalo cow or bull in this section.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>20. Amend § 1416.204 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (b)(16), remove “, and” and add a comma in its place;</AMDPAR>
                    <AMDPAR>b. In paragraph (b)(17), remove the period and add a comma in its place; and</AMDPAR>
                    <AMDPAR>c. Add paragraphs (b)(18) and (19).</AMDPAR>
                    <P>The additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.204 </SECTNO>
                        <SUBJECT>Covered livestock.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(18) Adult water buffalo cows and bulls, and</P>
                        <P>(19) Non-adult water buffalo.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1416.205 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>21. Amend § 1416.205 in paragraph (a)(3)(i) by removing “8” and add “4” in its place.</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1416.206 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>22. Amend § 1416.206 in paragraph (a) by removing “for the 2019 and subsequent program years”.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>23. Amend § 1416.207 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (a):</AMDPAR>
                    <AMDPAR>i. Remove the cross-reference “paragraphs (f) or (h)” and add the cross-reference “paragraph (g) or (i)” in its place;</AMDPAR>
                    <AMDPAR>ii. Add “a “2-month” payment,” after “a “1-month” payment,”; and</AMDPAR>
                    <AMDPAR>iii. Remove the cross-reference “paragraphs (b) through (e)” and add the cross-reference “paragraphs (b) through (f)” in its place;</AMDPAR>
                    <AMDPAR>b. In paragraph (b);</AMDPAR>
                    <AMDPAR>i. Remove the cross-reference “paragraph (h)” and add the cross-reference “paragraph (i)” in its place; and</AMDPAR>
                    <AMDPAR>ii. Remove “8” and add “4” in its place;</AMDPAR>
                    <AMDPAR>c. Redesignate paragraphs (c) through (m) as paragraphs (d) through (n);</AMDPAR>
                    <AMDPAR>d. Add new paragraph (c);</AMDPAR>
                    <AMDPAR>e. In newly redesignated paragraphs (d), (e), and (f), and paragraph (g) introductory text, remove the cross-reference “paragraph (h)” and add the cross-reference “paragraph (i)” in its place;</AMDPAR>
                    <AMDPAR>f. In newly redesignated paragraph (g)(1), remove the cross-reference “paragraph (i)” and add the cross-reference “paragraph (j)” in its place;</AMDPAR>
                    <AMDPAR>g. In newly redesignated paragraph (g)(2), remove the cross-reference “paragraph (l)” and add the cross-reference “paragraph (m)” in its place;</AMDPAR>
                    <AMDPAR>h. In newly redesignated paragraph (i), remove the cross-reference “paragraph (f)” and add the cross-reference “paragraph (g)” in its place;</AMDPAR>
                    <AMDPAR>i. In newly redesignated paragraph (j)(2), remove the cross-reference “paragraph (j)” and add the cross-reference “paragraph (k)” in its place;</AMDPAR>
                    <AMDPAR>j. In newly redesignated paragraphs (j)(3) and (m)(3), remove the cross-reference “paragraph (k)” and add the cross-reference “paragraph (l)” in its place; and</AMDPAR>
                    <AMDPAR>k. In newly redesignated paragraph (n)(3), remove the cross-reference “paragraph (i)” and add the cross-reference “paragraph (j)” in its place.</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.207 </SECTNO>
                        <SUBJECT>Payment calculation.</SUBJECT>
                        <STARS/>
                        <P>(c) To be eligible to receive a 2-month payment, that is a payment equal to the monthly feed cost as determined under paragraph (i) of this section, the eligible livestock producer must own or lease grazing land or pastureland that is physically located in a county that is rated by the U.S. Drought Monitor as having at least a D2 severe drought (intensity) in any area of the county for at least 7 of the previous 8 consecutive weeks during the normal grazing period for the specific type of grazing land or pastureland in the county.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart D—Livestock Indemnity Program</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>24. Amend § 1416.302 as follows:</AMDPAR>
                    <AMDPAR>a. Add the definitions of “Adult alpaca”, “Adult caribou”, “Adult deer”, “Adult elk”, “Adult equine”, “Adult goat, buck”, “Adult goat, nanny”, “Adult llama”, “Adult sheep, ewe”, “Adult sheep, ram”, “Adult swine, boars or barrows”, “Adult swine, sows or gilts”, “Adult water buffalo bull”, and “Adult water buffalo cow” in alphabetical order;</AMDPAR>
                    <AMDPAR>b. Revise the definition of “Application”;</AMDPAR>
                    <AMDPAR>c. Add the definitions of “Birthing factor” and “Bred” in alphabetical order;</AMDPAR>
                    <AMDPAR>d. Remove the definitions of “Buck”, “Equine animal”, and “Ewe”;</AMDPAR>
                    <AMDPAR>e. Add the definition of “Gestating” in alphabetical order;</AMDPAR>
                    <AMDPAR>f. Remove the definitions of “Kid”, “Lamb”, and “Nanny”;</AMDPAR>
                    <AMDPAR>
                        g. Add the definitions of “National average market value”, “Non-adult alpaca”, “Non-adult caribou”, “Non-adult deer”, “Non-adult elk”, “Non-adult equine”, “Non-adult goat, slaughter goat or kid”, “Non-adult llama”, “Non-adult sheep, lamb”, “Non-adult swine, suckling or nursery pig”, “Non-adult swine, lightweight barrow 
                        <PRTPAGE P="42327"/>
                        or gilt”, “Non-adult water buffalo”, and “Program year” in alphabetical order;
                    </AMDPAR>
                    <AMDPAR>h. Remove the definition of “Ram”; and</AMDPAR>
                    <AMDPAR>i. Add the definitions of “Reliable record or documentation”, “Unborn death losses”, and “Verifiable record or documentation” in alphabetical order.</AMDPAR>
                    <P>The additions and revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.302 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Adult alpaca</E>
                             means a male or female of that species that is at least 1 year old and used for breeding purposes.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Adult caribou</E>
                             means a male or female of that species that is of breeding age, at least 1.5 years old. This term includes adult reindeer, which are the same species.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Adult deer</E>
                             means a male or female of that species that is of breeding age, at least 6 months old.
                        </P>
                        <P>
                            <E T="03">Adult elk</E>
                             means a male or female of that species that is of breeding age, at least 1.5 years old.
                        </P>
                        <P>
                            <E T="03">Adult equine</E>
                             means a male or female domesticated horse, mule, or donkey that is of breeding age, at least 1 year old.
                        </P>
                        <P>
                            <E T="03">Adult goat, buck</E>
                             means a male goat that is of breeding age, at least 1 year old.
                        </P>
                        <P>
                            <E T="03">Adult goat, nanny</E>
                             means an adult female goat that is of breeding age, at least 1 year old.
                        </P>
                        <P>
                            <E T="03">Adult llama</E>
                             means a male or female of that species that is of breeding age, at least 1 year old.
                        </P>
                        <P>
                            <E T="03">Adult sheep, ewe</E>
                             means an adult female sheep that is of breeding age, at least 1 year old.
                        </P>
                        <P>
                            <E T="03">Adult sheep, ram</E>
                             means a male sheep that is of breeding age, at least 1 year old.
                        </P>
                        <P>
                            <E T="03">Adult swine, boars or barrows</E>
                             means male swine further delineated in weight classes 151 to 450 pounds and 451 pounds or more.
                        </P>
                        <P>
                            <E T="03">Adult swine, sows or gilts</E>
                             means female swine of breeding age further delineated in weight classes 151 to 450 pounds and 451 pounds or more.
                        </P>
                        <P>
                            <E T="03">Adult water buffalo bull</E>
                             means a male animal of that breed that was at least 2 years old and used for breeding purposes.
                        </P>
                        <P>
                            <E T="03">Adult water buffalo cow</E>
                             means a female animal of that breed that had delivered one or more offspring before it died or was injured and sold at a reduced price. A first-time bred water buffalo heifer is also considered an adult water buffalo cow if it was pregnant at the time it died or was sold at a reduced price.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Application</E>
                             means the LIP Notice of Loss and Application for Payment forms.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Birthing factor</E>
                             means:
                        </P>
                        <P>(1) The factor established by 7 U.S.C. 9081(b)(5)(C) for cattle, bison, horses, sheep, and swine; or</P>
                        <P>(2) The factor established by CCC that is equal to the average number of birthed animals for one gestational cycle for other species of livestock, as determined by CCC.</P>
                        <STARS/>
                        <P>
                            <E T="03">Bred</E>
                             means that an eligible adult female livestock has been exposed to an adult male breeding animal and is gestating or deliberately bred through controlled reproduction. This term does not apply to poultry.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Gestating</E>
                             means the period of pregnancy of female livestock, excluding poultry, which is the time between conception and birth.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">National average market value</E>
                             means livestock values established by CCC based on national market data provided by USDA's National Agricultural Statistical Service (NASS) or Agricultural Marketing Service (AMS) for the applicable period.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Non-adult alpaca</E>
                             means an animal that on or before the beginning date of the eligible adverse weather or loss condition does not meet the definition of adult alpaca.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Non-adult caribou</E>
                             means a male or female of that species that does not meet the definition of an adult caribou. The term includes non-adult reindeer, which are the same species.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Non-adult deer</E>
                             means a male or female of that species that does not meet the definition of an adult deer.
                        </P>
                        <P>
                            <E T="03">Non-adult elk</E>
                             means a male or female of that species that does not meet the definition of an adult elk.
                        </P>
                        <P>
                            <E T="03">Non-adult equine</E>
                             means a male or female domesticated horse, mule, or donkey that does not meet the definition of an adult equine.
                        </P>
                        <P>
                            <E T="03">Non-adult goat, slaughter goat or kid</E>
                             means a goat less than 1 year old.
                        </P>
                        <P>
                            <E T="03">Non-adult llama</E>
                             means a male or female of that species that does not meet the definition of an adult llama.
                        </P>
                        <P>
                            <E T="03">Non-adult sheep, lamb</E>
                             means a sheep less than 1 year old.
                        </P>
                        <P>
                            <E T="03">Non-adult swine, suckling or nursery pig</E>
                             means a young piglet weighing less than 50 pounds.
                        </P>
                        <P>
                            <E T="03">Non-adult swine, lightweight barrow or gilt</E>
                             means a castrated male swine (barrow) or a female swine that has not given birth (gilt), weighing 50 to 150 pounds.
                        </P>
                        <P>
                            <E T="03">Non-adult water buffalo</E>
                             means an animal of that breed that does not meet the definition of adult water buffalo cow or bull. Non-adult water buffalo are further delineated by weight categories of either less than 400 pounds or 400 pounds or more at the time they died or were sold at a reduced price.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Program year</E>
                             means the calendar year the loss occurred.
                        </P>
                        <P>
                            <E T="03">Reliable record or documentation</E>
                             means any non-verifiable document provided by the producer that reasonably supports the eligible loss as determined acceptable by CCC.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Unborn death losses</E>
                             means losses of eligible livestock, excluding poultry, that was gestating on the date of the death of the eligible adult female livestock due to an eligible loss condition.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Verifiable record or documentation</E>
                             means a document provided by the producer that can be verified by CCC through an independent source.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>25. Amend § 1416.304 as follows:</AMDPAR>
                    <AMDPAR>a. Revise paragraphs (a), (d), and (e);</AMDPAR>
                    <AMDPAR>b. Redesignate paragraph (f) as paragraph (g);</AMDPAR>
                    <AMDPAR>c. Add new paragraph (f); and</AMDPAR>
                    <AMDPAR>d. In newly redesignated paragraph (g), add a sentence at the end of the paragraph.</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.304 </SECTNO>
                        <SUBJECT> Eligible livestock.</SUBJECT>
                        <P>(a) To be considered eligible livestock for livestock owners, the kind of livestock must be adult or non-adult alpacas, dairy cattle, beef cattle, beefalo, bison, buffalo, caribou, elk, equine, llamas, sheep, goats, swine, deer, or water buffalo; or emus, poultry, or ostriches; and meet all the conditions in paragraph (c) of this section.</P>
                        <STARS/>
                        <P>(d) The following categories of animals owned by a livestock owner are eligible livestock and calculations of eligibility for payments will be calculated separately for each producer with respect to each category:</P>
                        <P>(1) Adult alpacas;</P>
                        <P>(2) Adult beef bulls;</P>
                        <P>
                            (3) Adult beef cows;
                            <PRTPAGE P="42328"/>
                        </P>
                        <P>(4) Adult beefalo bulls;</P>
                        <P>(5) Adult beefalo cows;</P>
                        <P>(6) Adult buffalo or bison bulls;</P>
                        <P>(7) Adult buffalo or bison cows;</P>
                        <P>(8) Adult caribou;</P>
                        <P>(9) Adult dairy bulls;</P>
                        <P>(10) Adult dairy cows;</P>
                        <P>(11) Adult deer;</P>
                        <P>(12) Adult elk;</P>
                        <P>(13) Adult equine;</P>
                        <P>(14) Adult goats, bucks;</P>
                        <P>(15) Adult goats, nannies;</P>
                        <P>(16) Adult llamas;</P>
                        <P>(17) Adult sheep, ewes;</P>
                        <P>(18) Adult sheep, rams;</P>
                        <P>(19) Adult swine, boars or barrows, 151 to 450 pounds;</P>
                        <P>(20) Adult swine, boars or barrows, 451 pounds or more;</P>
                        <P>(21) Adult swine, sows or gilts, 151 to 450 pounds;</P>
                        <P>(22) Adult swine, sows or gilts, 451 pounds or more;</P>
                        <P>(23) Adult water buffalo bull;</P>
                        <P>(24) Adult water buffalo cow;</P>
                        <P>(25) Chickens, broilers, pullets (regular size), 4.26 to 6.25 pounds;</P>
                        <P>(26) Chickens, chicks;</P>
                        <P>(27) Chickens, layers;</P>
                        <P>(28) Chickens, pullets or Cornish hens (small size), less than 4.26 pounds;</P>
                        <P>(29) Chickens, roasters, 6.26 to 7.75 pounds;</P>
                        <P>(30) Chickens, super roasters or parts, 7.76 pounds or more;</P>
                        <P>(31) Ducks;</P>
                        <P>(32) Ducks, ducklings;</P>
                        <P>(33) Emus;</P>
                        <P>(34) Geese, goose;</P>
                        <P>(35) Geese, gosling;</P>
                        <P>(36) Non-adult alpacas;</P>
                        <P>(37) Non-adult beef cattle, less than 400 pounds;</P>
                        <P>(38) Non-adult beef cattle, 400 to 799 pounds;</P>
                        <P>(39) Non-adult beef cattle, 800 pounds or more;</P>
                        <P>(40) Non-adult beefalo, less than 400 pounds;</P>
                        <P>(41) Non-adult beefalo, 400 to 799 pounds;</P>
                        <P>(42) Non-adult beefalo, 800 pounds or more;</P>
                        <P>(43) Non-adult buffalo or bison, less than 400 pounds;</P>
                        <P>(44) Non-adult buffalo or bison, 400 to 799 pounds;</P>
                        <P>(45) Non-adult buffalo or bison, 800 pounds or more;</P>
                        <P>(46) Non-adult caribou;</P>
                        <P>(47) Non-adult dairy cattle, less than 400 pounds;</P>
                        <P>(48) Non-adult dairy cattle, 400 to 799 pounds;</P>
                        <P>(49) Non-adult dairy cattle, 800 pounds or more;</P>
                        <P>(50) Non-adult deer;</P>
                        <P>(51) Non-adult elk;</P>
                        <P>(52) Non-adult equine;</P>
                        <P>(53) Non-adult llamas;</P>
                        <P>(54) Non-adult goats, slaughter or goats or kids;</P>
                        <P>(55) Non-adult sheet, lambs;</P>
                        <P>(56) Non-adult swine, suckling or nursery pigs, less than 50 pounds;</P>
                        <P>(57) Non-adult swine, lightweight barrows or gilts, 50 to 100 pounds;</P>
                        <P>(58) Non-adult water buffalo, less than 400 pounds;</P>
                        <P>(59) Non-adult water buffalo, 400 to 799 pounds;</P>
                        <P>(60) Non-adult water buffalo, 800 pounds or more;</P>
                        <P>(61) Ostriches;</P>
                        <P>(62) Turkeys, poults; and</P>
                        <P>(63) Turkeys, toms, fryers, and roasters.</P>
                        <P>(e) The following categories of animals are eligible livestock for contract growers and calculations of eligibility for payments will be calculated separately for each producer with respect to each category:</P>
                        <P>(1) Adult swine, boars or barrows, 151 to 450 pounds;</P>
                        <P>(2) Adult swine, boars or barrows, 451 pounds or more;</P>
                        <P>(3) Adult swine, sows or gilts, 151 to 450 pounds;</P>
                        <P>(4) Adult swine, sows or gilts, 451 pounds or more;</P>
                        <P>(5) Chickens, broilers, pullets (regular size), 4.26 to 6.25 pounds;</P>
                        <P>(6) Chickens, chicks;</P>
                        <P>(7) Chickens, layers;</P>
                        <P>(8) Chickens, pullets or Cornish hens (small size), less than 4.26 pounds;</P>
                        <P>(9) Chickens, roasters, 6.26 to 7.75 pounds;</P>
                        <P>(10) Chickens, super roasters or parts, 7.76 pounds or more;</P>
                        <P>(11) Ducks;</P>
                        <P>(12) Ducks, ducklings;</P>
                        <P>(13) Geese;</P>
                        <P>(14) Non-adult swine, suckling or nursery pigs, less than 50 pounds;</P>
                        <P>(15) Non-adult swine, lightweight barrows or gilts, 50 to 150 pounds;</P>
                        <P>(16) Turkeys, poults; and</P>
                        <P>(17) Turkeys, toms, fryers, and roasters.</P>
                        <P>(f) To be eligible for unborn death loss compensation in accordance with § 1416.306(h), eligible livestock includes adult female livestock that were gestating on the date of death and that died as a direct result of an eligible loss condition in the program year for which benefits are sought. Eligible adult livestock categories for unborn death losses include alpacas, beef cattle, beefalo, buffalo, bison, caribou, dairy cattle, deer, elk, equine, goats, llamas, sheep, swine, water buffalo, and any other livestock determined eligible by CCC, excluding poultry. Losses must have been incurred on or after January 1, 2024, and calculations of eligibility for payments will be determined separately for each producer.</P>
                        <P>(g) * * * Ineligible livestock for unborn death loss compensation include injured livestock that were sold due to an eligible livestock condition and livestock that are stillborn or aborted from adult females that did not die as a result of an eligible loss condition.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>26. Amend § 1416.305 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (c), remove the words “for losses apparent in 2024 and subsequent years, by” and add “, to FSA” in their place;</AMDPAR>
                    <AMDPAR>b. In paragraph (d)(8) introductory text, remove the period at the end of the paragraph and add a colon in its place;</AMDPAR>
                    <AMDPAR>c. Redesignate paragraph (d)(10) as paragraph (d)(11);</AMDPAR>
                    <AMDPAR>d. Add new paragraph (d)(10);</AMDPAR>
                    <AMDPAR>e. In paragraph (g) introductory text, add the words “an eligible” before the word “disease”; and</AMDPAR>
                    <AMDPAR>f. Add paragraphs (k) and (l).</AMDPAR>
                    <P>The additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.305 </SECTNO>
                        <SUBJECT>Application process.</SUBJECT>
                        <STARS/>
                        <P>(d) * * *</P>
                        <P>(10) For unborn death losses, additional information requested may include, but is not limited to verification of breeding records, exposure dates, herd health or veterinary documentation, inventory logs, or other supporting operational records consistent with the producer's normal business practices.</P>
                        <STARS/>
                        <P>(k) For program year 2026 and subsequent years, eligible livestock producers may provide verifiable sales documentation to support and request an alternative market price for their eligible livestock, by kind, type, and weight range as applicable, that may be used for the payment calculation in § 1416.306. Acceptable alternative price market documentation must be a verifiable sales transaction in the name of the producer applying for benefits. The documentation must include the name and contact information of the buyer; the producer applying for benefits as the seller; the number of livestock sold and the market price received per head by livestock kind, type, and weight class, as applicable; and the location and date of the sale, which must be within the same program year of the eligible loss event.</P>
                        <P>(l) For unborn livestock death losses:</P>
                        <P>
                            (1) For program years 2024 and 2025, eligible producers with an approved application that contains eligible livestock death losses for the livestock categories of alpacas, caribou, deer, elk, 
                            <PRTPAGE P="42329"/>
                            equine, llamas or swine may revise their 2024 or 2025 application for payment by a deadline established and announced by CCC to include a certification of the number of eligible livestock for which benefits were requested and approved that were female for purposes of determining eligibility for an additional payment for unborn death losses as calculated in accordance with § 1416.306(i);
                        </P>
                        <P>(2) For program years 2024 and 2025, producers with an approved application that contains eligible livestock death losses for the livestock categories of adult beef, beefalo, bison, buffalo, dairy, or water buffalo cows, nanny goats, and ewes (sheep) are not required to take additional action for purposes of determining eligibility for an additional payment for unborn death losses as calculated in accordance with § 1416.306(i); and</P>
                        <P>(3) For program year 2026 and subsequent years, eligible producers with eligible livestock death losses must certify on the application for payment, the number of adult female livestock that were bred and gestating on the date of death for purposes of determining eligibility for an additional payment for unborn death losses as calculated in accordance with § 1416.306(i).</P>
                        <P>(i) CCC may request additional supporting documentation from eligible livestock producers or conduct spot checks to confirm that livestock were gestating at the time of the eligible loss of the adult female. Additional information requested includes, but is not limited to, verification of breeding records, exposure dates, herd health or veterinary documentation, inventory logs, and other supporting operational records consistent with the producer's normal business practices. A spot check or request for additional information is appropriate when CCC identifies any of the following:</P>
                        <P>(A) Missing, inconsistent, or incomplete breeding or inventory records;</P>
                        <P>(B) Reported death losses that appear excessive or outside normal expectations for the operation type, size, or production practices;</P>
                        <P>(C) Conflicting information between the application, supporting documentation, or prior-year program participation;</P>
                        <P>(D) Patterns of repeated corrections, revisions, or documentation gaps by the producer; or</P>
                        <P>(E) Situations where CCC has reason to question whether livestock were bred at the time of loss based on reported exposure dates, breeding windows, or herd management practices.</P>
                        <P>(ii) If discrepancies are identified, further documentation may be requested and adjustments may be made to approved death loss numbers.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>27. Revise § 1416.306 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1416.306 </SECTNO>
                        <SUBJECT>Payment calculation.</SUBJECT>
                        <P>(a) Under this subpart, separate payment rates for eligible livestock owners and eligible livestock contract growers are specified in paragraphs (c) through (f) of this section, respectively. Payments for death losses are calculated by multiplying the national payment rate for each livestock category by the number of eligible livestock in excess of normal mortality in each category that died as a result of an eligible loss condition. Normal mortality for each livestock category will be determined by CCC on a State-by-State basis using local data sources including, but not limited to, State livestock organizations and the Cooperative Extension Service for the State. Adjustments will be applied as specified in paragraph (g) of this section.</P>
                        <P>(b) The market values of livestock, by kind, type, and weight class, as applicable, for the establishment of payment rates used in the payment calculation, are determined using the higher of:</P>
                        <P>(1) The national average market value by livestock kind, type, and weight class, at the beginning of the program year based on the prior-year market data as determined by CCC;</P>
                        <P>(2) The national average market value by livestock kind, type, and weight class, at the end of the program year based on the current-year market data, as determined by CCC;</P>
                        <P>(3) A producer's verifiable market value for livestock of the same kind, type, and weight class, based on the market value closest to the date of loss or date of event that caused the injury, specific to the producer's operation and program year, established in accordance with § 1416.305(k), not to exceed 145 percent of the higher of the national average market values established in accordance with paragraphs (b)(1) and (2) of this section; or</P>
                        <P>(4) Another price approved by CCC based on data showing market value the day before the livestock loss or the day before the date of the event that caused the loss.</P>
                        <P>(c) For losses due to an eligible adverse weather event or eligible disease, the LIP payment rate for eligible livestock owners is based on 75 percent of the determined market value of the applicable livestock kind, type, and weight class in accordance with paragraph (b) of this section.</P>
                        <P>(d) For losses due to an eligible attack, the LIP payment rate for eligible livestock owners is based on 100 percent of the determined market value of the applicable livestock kind, type, and weight class in accordance with paragraph (b) of this section.</P>
                        <P>(e) For losses due to an eligible adverse weather event or eligible disease, the LIP national payment rate for eligible livestock contract growers is based on 75 percent of the average income loss sustained by the contract grower with respect to the dead livestock. The rate that applies is based on the type, class, and weight of the animal at the time of the eligible loss condition and death.</P>
                        <P>(f) For losses due to an eligible attack, the LIP payment rate for eligible livestock contract growers is based on 100 percent of the average income loss sustained by the contract grower based on the applicable livestock kind, type, and weight of the animal at the time of the eligible loss condition and death.</P>
                        <P>(g) The LIP payment calculated for eligible livestock contract growers will be reduced by the amount the participant received from the party who contracted with the producer to raise the livestock for the loss of income from the dead livestock.</P>
                        <P>(h) Payments to livestock owners for losses due to sale of livestock at a reduced price because of injury from an eligible loss condition are calculated by multiplying the payment rate for each livestock category by the number of eligible livestock sold at a reduced price as a result of an eligible loss condition, minus the gross amount the eligible livestock owner received for the livestock up to the applicable established payment rate. In the event livestock sells for a reduced price that is in excess of the established payment rate, the payment rate will be subtracted, resulting in no payment for that livestock.</P>
                        <P>(i) Payments to livestock owners and contract growers for eligible unborn death losses are calculated as follows:</P>
                        <P>(1) For program year 2024 and 2025, multiplying the number of eligible adult female livestock death losses, including losses due to eligible attacks, as provided in § 1416.305(l)(1), excluding swine, after normal mortality, by 40 percent of the payment rate established in accordance with paragraph (c) or (e) of this section for the livestock category, multiplied by the applicable birthing factor in paragraph (j) of this section;</P>
                        <P>
                            (2) For program year 2024 and 2025, multiplying the number of eligible adult female livestock death losses, including losses due to eligible attacks, as provided in § 1416.305(l)(2), including 
                            <PRTPAGE P="42330"/>
                            swine, after normal mortality, by 85 percent of the payment rate established in accordance with paragraph (c) or (e) of this section for the lowest weight class of the same kind and type of livestock, multiplied by the applicable birthing factor in paragraph (j) of this section; and
                        </P>
                        <P>(3) For program year 2026 and subsequent years, multiplying the number of eligible adult female livestock death losses that were bred and gestating at the time of death or injury, after normal mortality, by 85 percent of the payment rate established in accordance with paragraphs (c) through (f) of this section for the lowest weight class of the same kind and type of livestock multiplied by the applicable birthing factor in paragraph (j) of this section.</P>
                        <P>(j) The birthing factor for unborn livestock loss payment calculation is:</P>
                        <P>(1) One for cattle (beef and dairy), bison, buffalo, beefalo, water buffalo, alpacas, caribou, horses, llamas, and elk;</P>
                        <P>(2) Two for deer, goats, and sheep;</P>
                        <P>(3) Twelve for swine; and</P>
                        <P>(4) The factor established by CCC for any other livestock determined eligible by CCC.</P>
                    </SECTION>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart E—Tree Assistance Program</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>28. Amend § 1416.400 as follows:</AMDPAR>
                    <AMDPAR>a. Revise paragraph (b); and</AMDPAR>
                    <AMDPAR>b. Remove paragraph (c).</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1416.400 </SECTNO>
                        <SUBJECT>Applicability.</SUBJECT>
                        <STARS/>
                        <P>(b) Eligible orchardists and nursery tree growers will be compensated as specified in § 1416.406 for eligible tree, bush, and vine losses in excess of normal mortality, or, where applicable, damage in excess of normal mortality and normal damage, that occurred in the calendar year (or loss period in the case of plant disease) for which benefits are being requested and as a direct result of a natural disaster.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>29. Amend § 1416.403 by revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1416.403 </SECTNO>
                        <SUBJECT>Eligible losses.</SUBJECT>
                        <P>(a) To qualify for any assistance under this subpart, except for assistance under § 1416.400(c), the eligible orchardist or nursery tree grower must first have suffered a mortality loss on a stand in excess of normal mortality as a result of a natural disaster as determined by CCC.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1416.406 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>30. Amend § 1416.406 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (a) introductory text, remove “15 percent damage or mortality (adjusted for normal damage or mortality)” and add “normal damage or normal mortality” in its place;</AMDPAR>
                    <AMDPAR>b. In paragraph (a)(2)(i), remove “50 percent” and add “65 percent” in its place; and</AMDPAR>
                    <AMDPAR>c. In paragraph (b), remove “15 percent mortality (adjusted for normal mortality)” and add “normal mortality” in its place.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1416">
                    <AMDPAR>31. Amend § 1416.407 by revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1416.407 </SECTNO>
                        <SUBJECT>Obligations of a participant.</SUBJECT>
                        <P>(a) Eligible orchardists and nursery tree growers must execute all required documents and complete the TAP-funded practice within 24 months of application approval unless the participant requests an extension and CCC determines the delay is due to circumstances beyond the participant's control. Extensions are limited to a maximum of 36 months.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 1421—GRAINS AND SIMILARLY HANDLED COMMODITIES—MARKETING ASSISTANCE LOANS AND LOAN DEFICIENCY PAYMENTS</HD>
                </PART>
                <REGTEXT TITLE="7" PART="1421">
                    <AMDPAR>32. The authority citation for part 1421 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>7 U.S.C. 9031-9040 and 15 U.S.C. 714b and c.</P>
                    </AUTH>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart A—General</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1421">
                    <AMDPAR>33. Amend § 1421.2 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), add the words “and direction” after the word “supervision”;</AMDPAR>
                    <AMDPAR>b. Revise paragraphs (b) through (d); and</AMDPAR>
                    <AMDPAR>c. Remove and reserve paragraph (e).</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1421.2 </SECTNO>
                        <SUBJECT>Administration.</SUBJECT>
                        <STARS/>
                        <P>(b) State and county committees, and representatives and their employees, do not have authority to modify or waive any of the provisions of the regulations set forth in this part.</P>
                        <P>(c) The State committee will take any action required by the regulations of this part that the county committee has not taken. The State committee will also:</P>
                        <P>(1) Correct, or require a county committee to correct, any action taken by such county committee that is not in accordance with the regulations of this part; or</P>
                        <P>(2) Require a county committee to withhold taking any action that is not in accordance with this part.</P>
                        <P>(d) No provision or delegation to an FSA State or county committee will preclude the Executive Vice President, CCC, or a designee, from determining any question arising under this part, or from reversing or modifying any determination made by an FSA State or county committee.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1421">
                    <AMDPAR>34. Amend § 1421.3 as follows:</AMDPAR>
                    <AMDPAR>a. Add the definition of “AMS” in alphabetical order;</AMDPAR>
                    <AMDPAR>b. Revise the definition of “Chickpeas”;</AMDPAR>
                    <AMDPAR>c. In the definition of “DMA Service County Office”, remove the words “accept, process, and disburse” and add the words “aid in the processing and servicing of” in their place;</AMDPAR>
                    <AMDPAR>d. Remove the definition of “Drawdown account”;</AMDPAR>
                    <AMDPAR>e. In the definition of “Electronic warehouse receipt (EWR)”, remove the words “Farm Service Agency” and add the words “Agricultural Marketing Service” in their place;</AMDPAR>
                    <AMDPAR>f. Add the definition of “Fedwire participant” in alphabetical order; and</AMDPAR>
                    <AMDPAR>g. In the definition of “Warehouse receipt”, in paragraph (2), remove “FSA” and add “AMS” in its place.</AMDPAR>
                    <P>The additions and revision read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1421.3 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">AMS</E>
                             means the Agricultural Marketing Service of the United States Department of Agriculture.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Chickpeas</E>
                             means any chickpea that meets the definition of a chickpea in accordance with the Federal Grain Inspection Service (FGIS) of AMS.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Fedwire participant</E>
                             means a banking institute that participates in the Fedwire Funds Service provided by the Federal Reserve Banks.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1421">
                    <AMDPAR>35. Amend § 1421.4 as follows:</AMDPAR>
                    <AMDPAR>a. Revise paragraph (a)(2)(vii); and</AMDPAR>
                    <AMDPAR>b. In paragraph (f), remove the word “and” and add the word “or” in its place.</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1421.4 </SECTNO>
                        <SUBJECT>Eligible producers.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(2) * * *</P>
                        <P>(vii) 7 CFR part 3—Debt Management;</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1421">
                    <AMDPAR>36. Amend § 1421.5 by adding paragraph (g) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1421.5 </SECTNO>
                        <SUBJECT>Eligible commodities.</SUBJECT>
                        <STARS/>
                        <P>(g) Any commodity pledged as collateral for a loan under this part must have been grown in the United States.</P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <PRTPAGE P="42331"/>
                    <SECTNO>§ 1421.6 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1421">
                    <AMDPAR>37. Amend § 1421.6 in paragraph (c)(3) by removing the word “decisionmaking” and adding “decision-making” in their place.</AMDPAR>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart B—Marketing Assistance Loans</HD>
                    <SECTION>
                        <SECTNO>§ 1421.107 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1421">
                    <AMDPAR>38. Amend § 1421.107 in paragraph (g)(2) by removing the words “the Kansas City Commodity Office” and adding “AMS” in their place.</AMDPAR>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart D—Grazing Payments for Wheat, Barley, Oats, and Triticale</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1421">
                    <AMDPAR>39. Amend § 1421.301 as follows:</AMDPAR>
                    <AMDPAR>a. Revise paragraphs (a) through (c); and</AMDPAR>
                    <AMDPAR>b. Remove paragraph (e).</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1421.301 </SECTNO>
                        <SUBJECT>Administration.</SUBJECT>
                        <P>(a) This subpart will be administered by the FSA under the general direction and supervision of the Executive Vice President, CCC, and will be carried out in the field by FSA State and county committees, respectively.</P>
                        <P>(b) State and county committees, and representatives and their employees, do not have the authority to modify or waive any of the provisions of the regulations in this part.</P>
                        <P>(c) The State committee will take any action required by the regulations of this part that the county committee has not taken. The State committee will also:</P>
                        <P>(1) Correct, or require a county committee to correct, any action taken by such county committee that is not in accordance with the regulations of this part; or</P>
                        <P>(2) Require a county committee to withhold taking any action which is not in accordance with the regulations of this part.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart E—Designated Marketing Associations for Peanuts</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1421">
                    <AMDPAR>40. Amend § 1421.417 by revising paragraphs (a), (b), (c), and (e) as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1421.417 </SECTNO>
                        <SUBJECT>Disbursing MAL and LDP proceeds.</SUBJECT>
                        <P>(a) A DMA must establish an account with the financial institution they wish to use from which to disburse MAL and LDP amounts to producers.</P>
                        <P>(b) CCC will determine whether the financial institute is a Fedwire participant and capable of receiving funds by wire.</P>
                        <P>(c) MAL and LDP proceeds are to be distributed to the producer within 3 work days from the date the DMA receives MAL or LDP proceeds from CCC, after deduction of authorized charges or fees for services.</P>
                        <STARS/>
                        <P>(e) CCC will provide the amount as necessary as funds are requested.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1421.418 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1421">
                    <AMDPAR>41. Amend § 1421.418 in paragraph (d) by removing the word “drawdown”.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 1427—COTTON</HD>
                </PART>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>42. The authority citation for part 1427 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 7 U.S.C. 7231-7237, 7931-7936, 9011, and 9031-40, 15 U.S.C. 714b and c.</P>
                    </AUTH>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart A—Nonrecourse Cotton Loan and Loan Deficiency Payments</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>43. Amend § 1427.2 as follows:</AMDPAR>
                    <AMDPAR>a. Revise paragraphs (a) through (d); and</AMDPAR>
                    <AMDPAR>b. Remove and reserve paragraph (e).</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1427.2 </SECTNO>
                        <SUBJECT>Administration.</SUBJECT>
                        <P>(a) The MAL and LDP Programs will be administered under the general supervision and direction of the Executive Vice President, CCC, and will be carried out in the field by FSA state and county committees, respectively.</P>
                        <P>(b) State and county committees, and representatives and their employees, do not have authority to modify or waive any of the provisions of the regulations set forth in this subpart.</P>
                        <P>(c) The State committee will take any action required by the regulations of this subpart that the county committee has not taken. The State committee will also:</P>
                        <P>(1) Correct, or require a county committee to correct, any action by such committee that is not in accordance with this subpart; or</P>
                        <P>(2) Require a county committee to withhold taking any action that is not in accordance with the regulations of this subpart.</P>
                        <P>(d) No provision or delegation to an FSA State or county committee will preclude the Executive Vice President, CCC, or a designee, from determining any question arising under this subpart, or from reversing or modifying any determination made by an FSA State or county committee.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>44. Amend § 1427.3 as follows:</AMDPAR>
                    <AMDPAR>a. Remove the definition of “Cotton commercial bank”; and</AMDPAR>
                    <AMDPAR>b. Revise the definitions of “Extra long staple (ELS) cotton” and “Upland cotton”.</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1427.3 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Extra long staple (ELS) cotton</E>
                             means cotton that is produced in the United States and is ginned on a roller gin and includes any of the following varieties:
                        </P>
                        <P>(1) American-Pima;</P>
                        <P>(2) All other varieties of the Gossypium barbadense species of cotton; and</P>
                        <P>(3) Any other variety of cotton, including first generation (F1) hybrids, in which one or more of these barbadense varieties predominate.</P>
                        <STARS/>
                        <P>
                            <E T="03">Upland cotton</E>
                             means planted and stub of the Gossypium species cotton that is produced in the United States and is ginned on either saw or roller gin and meets any of the following:
                        </P>
                        <P>(1) Is not a pure strain variety of the barbadense species or first generation (F1) hybrid thereof; or</P>
                        <P>(2) Is not any other variety of cotton in which one or more of the barbadense varieties predominate.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>45. Amend § 1427.4 by revising paragraph (a)(2)(iv) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1427.4 </SECTNO>
                        <SUBJECT>Eligible producer.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(2) * * *</P>
                        <P>(iv) 7 CFR part 3—Debt Management; and</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>46. Amend § 1427.5 by adding paragraph (o) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1427.5 </SECTNO>
                        <SUBJECT>General eligibility requirements.</SUBJECT>
                        <STARS/>
                        <P>(o) Cotton pledged as collateral for a loan under this part must have been grown in the United States.</P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1427.6 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>47. Amend § 1427.6 in paragraph (b) by removing the words “a cotton commercial bank” and adding the words “an approved CMA or loan servicing agent” in their place.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>48. Amend § 1427.10 by revising paragraph (a)(1) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1427.10 </SECTNO>
                        <SUBJECT>Approved storage.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>
                            (1) Persons desiring approval of their facilities should contact the Warehouse and Commodity Management Division, Agricultural Marketing Service, by calling (816) 926-6474 or emailing 
                            <E T="03">warehousing@usda.gov.</E>
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>49. Amend § 1427.19 as follows:</AMDPAR>
                    <AMDPAR>
                        a. In paragraph (c)(1)(ii), remove the words “commercial bank” and add “CMA” in their place;
                        <PRTPAGE P="42332"/>
                    </AMDPAR>
                    <AMDPAR>b. Revise paragraph (c)(2);</AMDPAR>
                    <AMDPAR>c. In paragraph (d), add the words “and ELS cotton” after the words “upland cotton”;</AMDPAR>
                    <AMDPAR>d. In paragraph (g), remove “§ 1427.25(e)” and add “§§ 1427.25(e) and 1427.26” in its place;</AMDPAR>
                    <AMDPAR>e. Revise paragraphs (h)(1)(i) and (ii);</AMDPAR>
                    <AMDPAR>f. In paragraph (i)(1), remove the words “An upland cotton loan” and add “A loan” in their place;</AMDPAR>
                    <AMDPAR>g. In paragraph (i)(2), add the words “or ELS cotton, as determined under § 1427.26,” after “§ 1427.25,”; and</AMDPAR>
                    <AMDPAR>h. Add paragraphs (i)(3) and (m).</AMDPAR>
                    <P>The revisions and additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1427.19 </SECTNO>
                        <SUBJECT>Repayment of MALs.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(2) For ELS cotton, at a level that is the lesser of:</P>
                        <P>(i) The loan level and charges, plus interest determined for such bales; or</P>
                        <P>(ii) The adjusted world price, as determined by CCC under § 1427.26, in effect on the day the repayment is received by the FSA county office, loan servicing agent, or cotton CMA that disbursed the loan.</P>
                        <STARS/>
                        <P>(h) * * *</P>
                        <P>(1) * * *</P>
                        <P>(i) The tariff storage rate for the warehouse for the current marketing year; or</P>
                        <P>(ii) The maximum storage rate set by area.</P>
                        <STARS/>
                        <P>(i) * * *</P>
                        <P>(3) In no case will the principal forgiven as part of a market gain for a bale exceed the LDP rate of the bale had it been offered for an LDP.</P>
                        <STARS/>
                        <P>(m) For upland cotton, if a lower adjusted world price is announced, as determined under § 1427.25, at any time during the 30 calendar days immediately following repayment of the marketing assistance loan, CCC shall provide a refund to the producer:</P>
                        <P>(1) The refund is an amount equal to the difference between the adjusted world price in effect at the time of loan redemption and the lowest adjusted world price during the 30 calendar days following the redemption date:</P>
                        <P>(i) To be issued at a frequency determined by CCC; but</P>
                        <P>(ii) Not less than every 30 days.</P>
                        <P>
                            (2) For the purposes of this paragraph (m), the term 
                            <E T="03">producer</E>
                             includes the remitter or redeemer of the marketing assistance loan.
                        </P>
                        <P>(3) For members of approved CMAs and loan servicing agents, all eligibility discrepancies in § 1425.17(d) must be resolved prior to refund being issued.</P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1427.20 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>50. Amend § 1427.20 in paragraph (b) by removing the words “Deficiencies of $24.99 or less” and add the words “Total aggregate deficiencies of $24.99 or less involving the same facts or basis of liability” in their place.</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1427.22 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>51. Amend § 1427.22 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), add the words “or ELS” after the word “upland”; and</AMDPAR>
                    <AMDPAR>b. In paragraph (b)(2), add the words “or ELS cotton” after the words “upland cotton”.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>52. Amend § 1427.23 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (a)(5), remove the word “and”;</AMDPAR>
                    <AMDPAR>b. In paragraph (a)(6), remove the period at the end of the paragraph and add “; and” in its place;</AMDPAR>
                    <AMDPAR>c. Add paragraph (a)(7);</AMDPAR>
                    <AMDPAR>d. In paragraph (c), remove the words “FSA county office, loan servicing agent, or cotton commercial bank” and add “FSA county office or loan servicing agent” in their place;</AMDPAR>
                    <AMDPAR>e. In paragraph (e)(2), remove the word “or”;</AMDPAR>
                    <AMDPAR>f. In paragraph (e)(3), remove the period at the end of the paragraph and add “; or” in its place; and</AMDPAR>
                    <AMDPAR>g. Add paragraph (e)(4).</AMDPAR>
                    <P>The additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1427.23 </SECTNO>
                        <SUBJECT>Cotton LDPs.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(7) For members of approved CMAs and loan servicing agents, all eligibility discrepancies in § 1425.17(d) must be resolved prior to an LDP being issued.</P>
                        <STARS/>
                        <P>(e) * * *</P>
                        <P>(4) Notwithstanding paragraphs (e)(1) through (3) of this section, if the applicable rate for upland cotton used to calculate the original LDP decreases within 30 calendar days of that rate being applied, CCC will issue an additional payment equal to the difference between the original rate and the lower rate for upland cotton in effect during that 30-day period, provided the producer remains otherwise eligible under this part.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1427.25 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>53. Amend § 1427.25 in paragraphs (a)(1) and (2) by removing the words “5 lowest-priced growths” and adding “3 lowest-priced growths” in their place.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1427">
                    <AMDPAR>54. Add § 1427.26 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1427.26 </SECTNO>
                        <SUBJECT>Determination of the prevailing world market price and the adjusted world price for ELS cotton.</SUBJECT>
                        <P>(a) CCC will determine the world market price for ELS cotton as follows:</P>
                        <P>(1) During the period when only one daily price quotation is available for each growth quoted for long staple cotton, CFR (cost and freight) Far East, the prevailing world market price for ELS cotton will be based on the average of the quotations for the preceding Friday through Thursday for the 3 lowest-priced growths of the growths quoted for long staple cotton, CFR Far East.</P>
                        <P>(2) During the period when both a price quotation for cotton for shipment no later than August or September of the current calendar year (current Far East shipment price) and a price quotation for cotton for shipment no earlier than October or November of the current calendar year (forward Far East shipment price) are available for growths quoted for long staple cotton, CFR Far East, the prevailing world market price for ELS cotton will be based on the average of the current Far East shipment prices for the preceding Friday through Thursday for the 3 lowest-priced growths of the growths quoted for long staple cotton, CFR Far East, except as specified in paragraph (c)(2)(iv) of this section.</P>
                        <P>(3) Quotes specified in paragraphs (a)(1) and (2) of this section may be adjusted to account for quality differences between the respective foreign growth and U.S. Pima, of the base quality.</P>
                        <P>(4) The ELS cotton prevailing world market price determined as specified in paragraph (a)(1) or (2) of this section is referred to as the “Extra-Long Staple Far East price” (ELSFE).</P>
                        <P>(5) If quotes are not available for 1 or more days in the 5-day period, the available quotes during the period will be used. If no quotes are available during the Friday through Thursday period, the prevailing world market price will be based on the best available world price information, as CCC determines.</P>
                        <P>(b) The ELS cotton prevailing world market price, adjusted as specified in paragraph (c) of this section (adjusted world price (AWP)), will apply to crops of ELS cotton.</P>
                        <P>(c) The ELS cotton AWP will equal the ELSFE determined as specified in paragraph (a) of this section, adjusted as follows:</P>
                        <P>
                            (1) ELSFE will be adjusted to U.S. location by deducting the average costs to market, including average transportation costs, as determined by CCC.
                            <PRTPAGE P="42333"/>
                        </P>
                        <P>(2) The prevailing world market price, adjusted as specified in paragraph (c)(1) of this section, may be further adjusted if it is determined that the adjustment is necessary to:</P>
                        <P>(i) Minimize potential loan forfeitures;</P>
                        <P>(ii) Minimize the accumulation of stocks of ELS cotton by the Federal Government;</P>
                        <P>(iii) Ensure that ELS cotton produced in the United States can be marketed freely and competitively, both domestically and internationally; and</P>
                        <P>(iv) Ensure an appropriate transition between current-crop and forward-crop price quotations, except that forward-crop price quotations may be used prior to July 31 of a marketing year only if there are insufficient current crop quotations and the forward-crop price quotation is the lowest such quotation available.</P>
                        <P>(d) The ELS cotton AWP, determined as specified in paragraph (c) of this section, and the amount of the additional adjustment determined as specified in paragraphs (e) and (f) of this section, will be announced, to the extent practicable, at 4 p.m. eastern time each Thursday. In the event that Thursday is a non-workday, the determination will be announced, to the extent practicable, at 8 a.m. eastern time the next work day.</P>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 1430—DAIRY PRODUCTS</HD>
                </PART>
                <REGTEXT TITLE="7" PART="1430">
                    <AMDPAR>55. The authority citation for part 1430 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>7 U.S.C. 9051-9060 and 9071 and 15 U.S.C. 714b and 714c.</P>
                    </AUTH>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart D—Dairy Margin Coverage Program</HD>
                    <SECTION>
                        <SECTNO>§ 1430.407 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1430">
                    <AMDPAR>56. Amend § 1430.407 in paragraph (i) by removing the cross-reference “paragraph (g)” and adding the cross-reference “paragraph (h)” in its place.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 1434—NONRECOURSE MARKETING ASSISTANCE LOANS AND LOAN DEFICIENCY PAYMENTS FOR HONEY</HD>
                </PART>
                <REGTEXT TITLE="7" PART="1434">
                    <AMDPAR>57. The authority citation for part 1434 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 7 U.S.C. 7231-7237, 7931-7936, and 9031-9040; and 15 U.S.C. 714b and c.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1434">
                    <AMDPAR>58. Amend § 1434.2 as follows:</AMDPAR>
                    <AMDPAR>a. Revise paragraphs (a), (b), (c) introductory text, and (d); and</AMDPAR>
                    <AMDPAR>b. Remove and reserve paragraph (e).</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1434.2 </SECTNO>
                        <SUBJECT>Administration.</SUBJECT>
                        <P>(a) The regulations of this part will be administered under the general supervision and direction of the Executive Vice President, CCC, and are carried out in the field by FSA State and county committees.</P>
                        <P>(b) State and county committees, and representatives and their employees, do not have the authority to modify or waive any of the provisions of the regulations set forth in this part.</P>
                        <P>(c) The State committee will take any action required by the regulations of this part that the county committee has not taken. The State committee will also:</P>
                        <STARS/>
                        <P>(d) No provision or delegation to an FSA State or county committee will preclude the Executive Vice President, CCC, or a designee, from determining any question arising under this part or from reversing or modifying any determination made by an FSA State or county committee.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1434.10 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1434">
                    <AMDPAR>59. Amend § 1434.10 in paragraph (f) by removing “part 1403” and adding “part 3” in its place.</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1434.11 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1434">
                    <AMDPAR>60. Amend § 1434.11 in paragraph (b) by removing “wil” and adding “will” in its place.</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1434.15 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1434">
                    <AMDPAR>61. Amend § 1434.15 in paragraph (i)(1)(ii)(E) by removing “part 1403” and adding “part 3” in its place.</AMDPAR>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1434.17 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1434">
                    <AMDPAR>62. Amend § 1434.17 in paragraph (b) by removing “part 1403” and adding “part 3” in its place.</AMDPAR>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 1435—SUGAR PROGRAM</HD>
                </PART>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>63. The authority citation for part 1435 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>7 U.S.C. 1359aa-1359jj, 7272, and 8110; 15 U.S.C. 714b and 714c.</P>
                    </AUTH>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart A—General Provisions</HD>
                    <SECTION>
                        <SECTNO>§ 1435.1 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>64. Amend § 1435.1 in paragraph (a) introductory text by adding the words “and the Agricultural Marketing Service (AMS)” after “(FSA)”.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>65. Amend § 1435.2 as follows:</AMDPAR>
                    <AMDPAR>a. Revise the definition of “Crop year”;</AMDPAR>
                    <AMDPAR>b. Add the definition of “Domestic sugar industry” in alphabetical order;</AMDPAR>
                    <AMDPAR>c. Revise the definition of “Imports”;</AMDPAR>
                    <AMDPAR>d. In the definition of “Market or marketing”, remove the words “Polyhydric Alcohol program” and add “Polyhydric Alcohol Program” in their place;</AMDPAR>
                    <AMDPAR>e. Add the definition of “New entrant” in alphabetical order;</AMDPAR>
                    <AMDPAR>f. In the definition of “Proportionate share”, add the words “in a proportionate share State” after “producer”;</AMDPAR>
                    <AMDPAR>g. In the definition of “Raw sugar”, add the words “regardless of polarity” after “quality”;</AMDPAR>
                    <AMDPAR>h. Add the definition of “Sugar Storage Agreement” in alphabetical order; and</AMDPAR>
                    <AMDPAR>i. In the definition of “U.S. market value”, remove the words “New York Board of Trade No. 14” and add “International Continental Exchange (ICE) No. 16” in their place.</AMDPAR>
                    <P>The additions and revision read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1435.2 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Crop year</E>
                             means, for sugar, the period from October 1 through September 30, inclusive, and is identified by the year in which harvest and processing of the crop begins. For example, the 2025 crop year for sugar beets or sugarcane begins on October 1, 2025, and refers to domestically grown sugar beets or sugar cane whose harvest and processing began in autumn 2025. Sugar from de-sugaring molasses is considered to be from the crop year the de-sugaring occurred.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Domestic sugar industry</E>
                             means domestic:
                        </P>
                        <P>(1) Sugar beet producers and processors;</P>
                        <P>(2) Producers and processors of sugar cane; and</P>
                        <P>(3) Refiners of raw cane sugar.</P>
                        <STARS/>
                        <P>
                            <E T="03">Imports</E>
                             means sugar originating in foreign countries or areas and entered, or to be entered, into the United States customs territory. Imports are considered entered in the month recorded on the Department of Homeland Security, U.S. Customs and Border Protection Entry Summary form 7501, or equivalent electronic form if using the Automated Broker Interface (ABI).
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">New entrant</E>
                             means an individual, corporation, or other entity that does not have an allocation and is not affiliated with any individual, corporation, or entity that has an allocation.
                        </P>
                        <STARS/>
                        <P>
                            <E T="03">Sugar Storage Agreement</E>
                             means the agreement between CCC and a warehouse operator that defines terms for storing and handling of CCC-owned sugar or sugar pledged as collateral for a CCC marketing assistance loan.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1435">
                    <PRTPAGE P="42334"/>
                    <AMDPAR>66. Amend § 1435.4 as follows:</AMDPAR>
                    <AMDPAR>a. Revise paragraphs (a), (b), and (d); and</AMDPAR>
                    <AMDPAR>b. Remove and reserve paragraph (e).</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1435.4 </SECTNO>
                        <SUBJECT>Administration.</SUBJECT>
                        <P>(a) This program will be administered under the general supervision and direction of the Executive Vice President, CCC, and will be carried out in the field by FSA State and county committees.</P>
                        <P>(b) State and county committees, and representatives and employees thereof, do not have authority to modify or waive any of the provisions of the regulations set forth in this part.</P>
                        <STARS/>
                        <P>(d) No provision or delegation herein to a State or county committee shall preclude the Executive Vice President, CCC, or a designee, from determining any question arising under this part or from reversing or modifying any State or county committee determination.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>67. Amend § 1435.5 by revising paragraph (d) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1435.5 </SECTNO>
                        <SUBJECT>Other regulations.</SUBJECT>
                        <STARS/>
                        <P>(d) Part 3—Debt Management.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart B—Sugar Loan Program</HD>
                    <SECTION>
                        <SECTNO>§ 1435.101 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>68. Amend § 1435.101 in paragraph (c) by adding “, regardless of storage location” at the end of the sentence.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>69. Amend § 1435.102 as follows:</AMDPAR>
                    <AMDPAR>a. Revise paragraph (c)(2);</AMDPAR>
                    <AMDPAR>b. In paragraph (c)(4), remove the word “and”;</AMDPAR>
                    <AMDPAR>c. In paragraph (c)(5), remove the period and add “; and” in its place;</AMDPAR>
                    <AMDPAR>d. Add paragraph (c)(6); and</AMDPAR>
                    <AMDPAR>e. In paragraph (d)(2) introductory text, add the words “and refined” after “Raw”.</AMDPAR>
                    <P>The revision and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1435.102 </SECTNO>
                        <SUBJECT>Eligibility requirements.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(2) Must be processed and owned by the eligible processor and stored in a CCC-approved warehouse, unless CCC and the warehouse operator agree, in writing, to store the sugar at another location in accordance with the Sugar Storage Agreement;</P>
                        <STARS/>
                        <P>(6) May not be pledged as collateral in a subsequent crop year.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>70. Amend § 1435.103 by adding paragraph (c)(4) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1435.103 </SECTNO>
                        <SUBJECT>Availability, disbursement, and maturity of loans.</SUBJECT>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(4) Sugar may not be pledged as collateral in a subsequent crop year.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>71. Amend § 1435.105 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (d) introductory text, remove the semicolon and add a colon in its place;</AMDPAR>
                    <AMDPAR>b. In paragraph (i)(1), remove “part 1403” and add “part 3” in its place; and</AMDPAR>
                    <AMDPAR>c. Revise paragraph (j).</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1435.105 </SECTNO>
                        <SUBJECT>Loan settlement and foreclosure.</SUBJECT>
                        <STARS/>
                        <P>(j) The CCC rates for the storage of forfeited sugar to approved warehouses for the 2025 crop year and each subsequent crop year will be at least:</P>
                        <P>(1) For refined sugar, 34 cents per hundredweight per month; and</P>
                        <P>(2) For raw cane sugar, 27 cents per hundredweight per month.</P>
                        <P>(3) For each of the 2012 through 2024 crop years, CCC shall establish rates for the storage of forfeited sugar in the same manner as was used on the day before the date of July 9, 2026.</P>
                        <P>(4) For sugar located in space not approved by CCC for storage, the payment rate will be zero until such time as the processor delivers such sugar to a CCC-approved warehouse or a location agreed to by CCC and the warehouse operator, accordance with the Sugar Storage Agreement.</P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1435.106 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>72. Amend § 1435.106 in paragraph (a) by removing the words “parts 3 and 1403” and adding “part 3” in their place.</AMDPAR>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart C—Information Reporting and Recordkeeping Requirements</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>73. Amend § 1435.200 by revising paragraph (i) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1435.200 </SECTNO>
                        <SUBJECT>Information reporting.</SUBJECT>
                        <STARS/>
                        <P>(i) Sugar beet processors, sugarcane processors, and sugarcane refiners will submit to CCC within 90 days of the company's annual year-end audit a report from an independent Certified Public Accountant certifying that the information submitted to CCC during the previous 12-month period is within 5 percent of the physical count of that same information conducted during the audit.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart D—Flexible Marketing Allotments For Sugar</HD>
                    <SECTION>
                        <SECTNO>§ 1435.302 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>74. Amend § 1435.302 in paragraph (a)(2) by removing the word “that” and adding “than” in its place.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>75. Amend § 1435.303 as follows:</AMDPAR>
                    <AMDPAR>a. Redesignate paragraph (d) as paragraph (e); and</AMDPAR>
                    <AMDPAR>b. Add new paragraph (d).</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1435.303 </SECTNO>
                        <SUBJECT>Adjustment of the overall allotment quantity.</SUBJECT>
                        <STARS/>
                        <P>(d) When making upward adjustments in allocations among beet processors, CCC will give priority to beet sugar processors with available sugar.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 1435.306 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>76. Amend § 1435.306 as follows:</AMDPAR>
                    <AMDPAR>a. Remove paragraph (g); and</AMDPAR>
                    <AMDPAR>b. Redesignate paragraph (h) as paragraph (g).</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>77. Amend § 1435.307 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), remove the word “allotment”; and</AMDPAR>
                    <AMDPAR>b. Revise paragraph (b)(4) and paragraph (f) introductory text.</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1435.307 </SECTNO>
                        <SUBJECT>Transfer of allocation.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(4) Allocation transfers will be effective on October 1 of the next fiscal year after the request is submitted to CCC.</P>
                        <STARS/>
                        <P>(f) If a processor of beet sugar purchases some, but not all, of the assets of another processor, then CCC will assign a pro rata portion of the allocation to the buyer to reflect the historical contribution of the sold facilities, unless the buyer and seller have agreed upon a different allocation amount, in which case CCC will transfer that amount agreed upon to the buyer.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>78. Amend § 1435.308 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (a) introductory text, remove the word “entrant”; and</AMDPAR>
                    <AMDPAR>b. Revise paragraph (d)(1).</AMDPAR>
                    <P>The revision reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1435.308 </SECTNO>
                        <SUBJECT>New entrants.</SUBJECT>
                        <STARS/>
                        <P>(d) * * *</P>
                        <P>
                            (1) Assign, upon the mutual agreement of new entrant and the current processor, an allocation to the buyer to reflect the historical contribution of the sold facilities, unless the buyer and seller have agreed upon 
                            <PRTPAGE P="42335"/>
                            a different allocation amount, in which case that agreed upon portion will instead be transferred; or
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>79. Amend § 1435.309 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraphs (c)(2) through (4), add the words “it shall” before the words “be reassigned”;</AMDPAR>
                    <AMDPAR>b. Remove paragraph (d);</AMDPAR>
                    <AMDPAR>c. Redesignate paragraph (e) as paragraph (d);</AMDPAR>
                    <AMDPAR>d. In newly redesignated paragraph (d)(2):</AMDPAR>
                    <AMDPAR>i. Remove “(e)(1)” and add “(d)(1)” in its place; and</AMDPAR>
                    <AMDPAR>ii. Add the words “it shall” before the words “be reassigned”;</AMDPAR>
                    <AMDPAR>e. In newly redesignated paragraph (d)(3), remove “(e)(1) and (e)(2)” and add “(d)(1) and (2)” in its place;</AMDPAR>
                    <AMDPAR>f. Add paragraphs (d)(4) and (5); and</AMDPAR>
                    <AMDPAR>g. Redesignate paragraph (f) as paragraph (e).</AMDPAR>
                    <P>The additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1435.309 </SECTNO>
                        <SUBJECT>Reassignment of deficits.</SUBJECT>
                        <STARS/>
                        <P>(d) * * *</P>
                        <P>(4) CCC will make an initial determination based on the World Agricultural Supply and Demand Estimates approved by the World Agricultural Outlook Board for January of the applicable crop year.</P>
                        <P>(5) CCC will provide an initial reassignment of allocations not later than 30 days after the publication of the January World Agricultural Supply and Demand Estimates report.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart E—Disposition of CCC Inventory</HD>
                    <SECTION>
                        <SECTNO>§ 1435.401 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>80. Amend § 1435.401 in paragraph (a)(1) by adding the words “through crop year 2026,” after the word “Program”.</AMDPAR>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart F—Processor Sugar Payment-In-Kind (PIK) Program</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>81. Amend § 1435.501 by revising paragraph (a)(1)(ii) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1435.501 </SECTNO>
                        <SUBJECT>Bid submission procedures.</SUBJECT>
                        <P>(a) * * *</P>
                        <P>(1) * * *</P>
                        <P>(ii) The previous consecutive 3-year simple average sugar beet or sugarcane yield on that acreage while under contract. Years with no production contracted with a producer will not be considered. For first-time producers, the previous consecutive 3-year simple average sugar beet or sugarcane yield for all the producers under contract who delivered to the applicable factory will be used;</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart G—Feedstock Flexibility Program</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="1435">
                    <AMDPAR>82. Amend § 1435.600 as follows:</AMDPAR>
                    <AMDPAR>a. In paragraph (b)(1), remove “, an” and add “; and” in its place; and</AMDPAR>
                    <AMDPAR>b. Add paragraph (c).</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1435.600 </SECTNO>
                        <SUBJECT>General statement.</SUBJECT>
                        <STARS/>
                        <P>(c) This subpart will be applicable until the end of crop year 2026.</P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>William Beam,</NAME>
                    <TITLE>Executive Vice President, Commodity Credit Corporation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13878 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3411-E2-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Rural Business-Cooperative Service</SUBAGY>
                <CFR>7 CFR Part 4287</CFR>
                <DEPDOC>[Docket No. RBS-26-BUSINESS-0364]</DEPDOC>
                <RIN>RIN 0570-AB14</RIN>
                <SUBJECT>Revisions to the Biorefinery, Renewable Chemical, and Biobased Product Manufacturing Assistance Loan Program</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Rural Business—Cooperative Service, USDA</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Biorefinery, Renewable Chemical, and Biobased Product Manufacturing Program (also referred to as the Section 9003 program) provides loan guarantees up to $250 million to assist in the development, construction, and retrofitting of new and emerging technologies. These technologies are: advanced biofuels, renewable chemicals, and biobased products. Collectively, Rural Development's guaranteed loan programs assist in building and maintaining sustainable rural communities. This final rule incorporates revisions intended to clarify, improve, and enhance the delivery of the loan guarantee program.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective July 9, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Brian Wiles, Director of the Program Processing Division, Rural Business Cooperative Service, U.S. Department of Agriculture, 1400 Independence Ave. SW, Washington, DC 20250; telephone 405-612-4839; email: 
                        <E T="03">brian.wiles@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>The Biorefinery, Renewable Chemical, and Biobased Product Manufacturing Program, administered under 7 CFR 4279 Subpart C and 7 CFR 4287 Subpart D, provides loan guarantees up to $250 million to eligible applicants to develop advanced biofuels, renewable chemicals, and biobased-products manufacturing facilities to deliver new and innovative technologies. These loan guarantees assist to develop, build, or retrofit facilities to support new and emerging technologies and produce advanced biofuels, renewable chemicals, and biobased products.</P>
                <HD SOURCE="HD1">II. Summary of Changes to Rule</HD>
                <P>
                    This updated final rule for the Section 9003 program strengthens the $250 million loan guarantee framework for advanced biofuels, renewable chemicals, and biobased products by introducing critical integrity measures. These revisions to the regulation will strengthen oversight and management of the growing Section 9003 loan guarantee portfolios. The revisions aim to prevent fraud and abuse by barring any borrower or guarantor from remaining involved in a project if it results in a monetary loss to the Agency. These changes ensure that participants remain fully committed to the long-term success of their operations rather than relying on debt reductions or government-backed bailouts to mitigate poor performance. For example, consider a borrower with a failed project due to cost overruns or bad management. In this example, if the Agency pays the Lender's final loss claim, and the Lender writes down the borrower's debt, but the borrower continues operating the project, the government bore the cost of the borrower's poor management. If the Agency permits a borrower or guarantor to remain involved in a project following the Agency's loss, the borrower or guarantor may eventually profit from the project at the government's expense, effectively turning this government assistance into a grant. This arrangement creates perverse incentives for unethical parties to not execute their project to the best of their ability, seek to write down the loss paid by the taxpayer, and later earn a profit based on the government's loss. These regulatory changes close any loophole that would allow for a borrower or guarantor to later profit from a failed project funded by the Agency.
                    <PRTPAGE P="42336"/>
                </P>
                <HD SOURCE="HD2">1. Section 4287.345 Default by Borrower</HD>
                <P>Section 4287.345(c) is revised to prohibit debt write-downs when borrowers or guarantors retain decision-making authority.</P>
                <HD SOURCE="HD2">2. Section 4287.358 Prohibition Under Agency Programs</HD>
                <P>Section 4287.358(h) is added to prohibit borrowers and guarantors, as well as related parties with whom either the applicant or guarantor does not have an arm's length transaction relationship, from remaining involved in a project any time the Agency sustains a loss. The new section 4289.358(h) prevents entities from continuing to benefit from a project after the Agency has absorbed a financial loss on their behalf.</P>
                <HD SOURCE="HD1">III. Executive Orders</HD>
                <HD SOURCE="HD2">Executive Order 12372—Intergovernmental Review of Federal Programs</HD>
                <P>This program is not subject to the requirements of Executive Order 12372, “Intergovernmental Review of Federal Programs,” as implemented under USDA's regulations at 2 CFR 415, subpart C.</P>
                <HD SOURCE="HD2">Executive Order 12866—Regulatory Planning and Review</HD>
                <P>This rule has been determined to be not significant for purposes of Executive Order 12866 and, therefore, has not been reviewed by the Office of Management and Budget.</P>
                <HD SOURCE="HD2">Executive Order 12988—Civil Justice Reform</HD>
                <P>This rule has been reviewed under Executive Order 12988. In accordance with this rule: (1) unless otherwise specifically provided, all State and local laws that conflict with this rule will be preempted; (2) no retroactive effect will be given to this rule except as specifically prescribed in the rule; and (3) administrative proceedings of the National Appeals Division of the Department of Agriculture (7 CFR part 11) must be exhausted before bringing suit in court that challenges action taken under this rule.</P>
                <HD SOURCE="HD2">Executive Order 13132—Federalism</HD>
                <P>The policies contained in this rule do not have any substantial direct effect on 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. Nor does this rule impose substantial direct compliance costs on state and local governments. Therefore, consultation with the States is not required.</P>
                <HD SOURCE="HD2">Executive Order 13175—Consultation and Coordination With Indian Tribal Governments</HD>
                <P>This final rule has been reviewed in accordance with the requirements of Executive Order 13175, Consultation and Coordination with Indian Tribal Governments. Executive Order 13175 requires Federal agencies to consult and coordinate with Tribes on a government-to-government basis on policies that have Tribal implications, including regulations, legislative comments or proposed legislation, and other policy statements or actions that have substantial direct effects 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. Consultation is also required for any regulation that preempts Tribal law or that imposes substantial direct compliance costs on Indian Tribal governments and that is not required by statute.</P>
                <P>The Agency has determined that this final rule does not have Tribal implications that require formal Tribal consultation under Executive Order 13175. If a Tribe requests consultation, the RBCS will work with the Office of Tribal Relations to ensure meaningful consultation is provided where changes, additions and modifications identified herein are not expressly mandated by Congress.</P>
                <HD SOURCE="HD2">Assistance Listing Number</HD>
                <P>The Assistance Listing Number assigned to the Biorefinery, Renewable Chemical, and Biobased Product Manufacturing Program is 10.865.</P>
                <HD SOURCE="HD2">Civil Rights Impact Analysis</HD>
                <P>This Final Rule was reviewed in accordance with USDA Regulation 4300-4, Civil Rights Impact Analysis,” to identify any major civil rights impacts the rule might have on program participants on the basis of age, race, religion, color, national origin, sex, disability, genetic information, political beliefs, marital status, familial status, parental status, veteran status, religion, reprisal and/or resulting from all or a part of an individual's income being derived from any public assistance program. This Final rule is within a Guarantee-based program. Guarantees are not covered under Title VI of the Civil Rights Act of 1964, Section 504 of the Rehabilitation Act of 1973, and Title IX of the Education Amendments Act of 1972, as amended, when Federal assistance does not include insurance or interest credit loans. Lenders must comply with other applicable Federal laws, including Equal Employment Opportunities, the Equal Credit Opportunity Act, the Fair Housing Act, and the Civil Rights Act of 1964. Guaranteed loans that involve the construction of or addition to facilities that accommodate the public must comply with the Architectural Barriers Act Accessibility Standard. The borrower and lender are responsible for ensuring compliance with these requirements.</P>
                <HD SOURCE="HD2">Congressional Review Act</HD>
                <P>
                    Pursuant to the Congressional Review Act (5 U.S.C. 801 
                    <E T="03">et seq.</E>
                    ), the Office of Information and Regulatory Affairs designated this final rule as not a major rule, as defined by 5 U.S.C. 804(2).
                </P>
                <HD SOURCE="HD2">E-Government Act Compliance</HD>
                <P>Rural Development is committed to the E-Government Act, which requires Government agencies in general to provide the public the option of submitting information or transacting business electronically to the maximum extent possible and to promote the use of the internet and other information technologies to provide increased opportunities for citizen access to Government information and services, and for other purposes.</P>
                <HD SOURCE="HD2">National Environmental Policy Act</HD>
                <P>In accordance with the National Environmental Policy Act of 1969, Public Law 91-190, this final rule has been reviewed in accordance with 7 CFR part 1b (“National Environmental Policy Act”). The Agency has determined that (i) this action meets the criteria established in 7 CFR 1b and (ii) no extraordinary circumstances exist. Therefore, the Agency has determined that the action does not have a significant effect on the human environment, and therefore neither an Environmental Assessment nor an Environmental Impact Statement is required.</P>
                <HD SOURCE="HD2">Paperwork Reduction Act</HD>
                <P>This rule contains no reporting or recordkeeping provisions requiring Office of Management and Budget (OMB) approval under the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35).</P>
                <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
                <P>
                    The Regulatory Flexibility Act (5 U.S.C. 601-602) (RFA) generally requires an agency to prepare a regulatory flexibility analysis of any rule subject to notice and comment 
                    <PRTPAGE P="42337"/>
                    rulemaking requirements under the Administrative Procedure Act (“APA”) or any other statute. The Administrative Procedures Act exempts from notice and comment requirements rules “relating to agency management or personnel or to public property, loans, grants, benefits, or contracts” (5 U.S.C. 553(a)(2)), so an analysis has not been prepared for this rule.
                </P>
                <HD SOURCE="HD2">Severability</HD>
                <P>It is USDA's intention that the provisions of this rule shall operate independently of each other. In the event that this rule or any portion of this rule is ultimately declared invalid or stayed as to a particular provision, it is USDA's intent that the rule nonetheless be severable and remain valid with respect to those provisions not affected by a declaration of invalidity or stayed. USDA concludes it would separately adopt all of the provisions contained in this final rule.</P>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act (UMRA)</HD>
                <P>Title II of the UMRA,  Public Law 104-4, establishes requirements for Federal Agencies to assess the effects of their regulatory actions on State, local, and Tribal Governments and on the private sector. Under section 202 of the UMRA, Federal Agencies generally must prepare a written statement, including cost-benefit analysis, for proposed and Final Rules with “Federal mandates” that may result in expenditures to State, local, or Tribal Governments, in the aggregate, or to the private sector, of $100 million or more in any one-year. When such a statement is needed for a rule, section 205 of the UMRA generally requires a Federal Agency to identify and consider a reasonable number of regulatory alternatives and adopt the least costly, more cost-effective, or least burdensome alternative that achieves the objectives of the rule.</P>
                <P>This rule contains no Federal mandates (under the regulatory provisions of title II of the UMRA) for State, local, and Tribal Governments or for the private sector. Therefore, this rule is not subject to the requirements of sections 202 and 205 of the UMRA.</P>
                <HD SOURCE="HD2">USDA Non-Discrimination Statement</HD>
                <P>In accordance with Federal civil rights laws and USDA civil rights regulations and policies, the USDA, its Mission Areas, agencies, staff offices, employees, and institutions participating in or administering USDA programs are prohibited from discriminating based on race, color, national origin, religion, sex, disability, age, marital status, family/parental status, income derived from a public assistance program, political beliefs, or reprisal or retaliation for prior civil rights activity, in any program or activity conducted or funded by USDA (not all bases apply to all programs). Remedies and complaint filing deadlines vary by program or incident.</P>
                <P>
                    Persons with disabilities who require alternative means of communication to obtain program information (
                    <E T="03">e.g.,</E>
                     Braille, large print, audiotape, American Sign Language, etc.) should contact the State or local Agency that administers the program or contact USDA through the Telecommunications Relay Service at 711 (voice and TTY). Program information may be made available in languages other than English.
                </P>
                <P>
                    To file a program discrimination complaint, a complainant should complete a Form AD-3027, USDA Program Discrimination Complaint Form, which can be obtained online at 
                    <E T="03">https://www.usda.gov/sites/default/files/documents/ad-3027.pdf</E>
                     and at any USDA office or write a letter addressed to USDA and provide in the letter all of the information requested in the form. To request a copy of the complaint form, call (866) 632-9992. Submit your completed form or letter to USDA by:
                </P>
                <HD SOURCE="HD2">
                    a. 
                    <E T="03">Mail:</E>
                     U.S. Department of Agriculture, Office of the Assistant Secretary for Civil Rights, 1400 Independence Avenue SW, Mail Stop 9410, Washington, DC 20250-9410; or
                </HD>
                <P>
                    b. 
                    <E T="03">Fax:</E>
                     (202) 690-7442; or
                </P>
                <P>
                    c. 
                    <E T="03">Email:</E>
                      
                    <E T="03">program.intake@usda.gov</E>
                    .
                </P>
                <P>USDA is an equal opportunity provider, employer, and lender.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR 4287</HD>
                    <P>Community development, Economic development, Energy, Energy conservation, Grant programs, Loan programs, Loan programs—business, Loan programs—housing and community development, Renewable energy, Reporting and recordkeeping requirements, Rural areas.</P>
                </LSTSUB>
                <P>For the reasons stated in the preamble, the RBCS amends 7 CFR 4287 Subpart D as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 4287—SERVICING</HD>
                </PART>
                <REGTEXT TITLE="7" PART="4287">
                    <AMDPAR>1. The authority citation continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>5 U.S.C. 301; 7 U.S.C. 1932(a); 7 U.S.C. 1989</P>
                    </AUTH>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart D—Servicing Biorefinery, Renewable Chemical, and Biobased Manufacturing Assistance Guaranteed Loans</HD>
                </SUBPART>
                <REGTEXT TITLE="7" PART="4287">
                    <AMDPAR>2. Revise and republish § 4287.345(c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 4287.345 </SECTNO>
                        <SUBJECT>Default by Borrower.</SUBJECT>
                        <STARS/>
                        <P>(c) Debt write-downs for an existing borrower or guarantor, where the same owners or principals retain control of and decision-making authority for the business, are prohibited, except as directed or ordered under the Bankruptcy Code.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="4287">
                    <AMDPAR>3. Amend § 4287.358 by adding paragraph (h) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 4287.358 </SECTNO>
                        <SUBJECT>Determination of loss and payment.</SUBJECT>
                        <STARS/>
                        <P>(h) Borrowers and guarantors, as well as related parties with whom either the borrower or guarantor does not have an arm's length transaction relationship, are prohibited from remaining involved in a project any time the agency takes a loss. </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>Victoria Collin,</NAME>
                    <TITLE>Acting Administrator, Rural Business Cooperative Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13841 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-XY-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <CFR>10 CFR Parts 300, 451, 452, 455, 602, 605, 706, 708, 712, 719, 725, 727, 733, 760, 766, 782, 783, 784, 824, 840, 860, 861, 862, 950, 960, 963, 1009, 1015, 1016, 1045, 1046, and 1061</CFR>
                <DEPDOC>[Docket No. DOE-HQ-2025-0603]</DEPDOC>
                <RIN>RIN 1990-AA54</RIN>
                <SUBJECT>Zero-Based Regulating</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Energy (DOE).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Withdrawal of direct final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Due to receipt of adverse comments, the Department of Energy (DOE) is withdrawing the direct final rule titled “Zero-Based Regulating,” which published on May 29, 2026.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective July 9, 2026, DOE withdraws the direct final rule published at 91 FR 31869 on May 29, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. Clara Wheelock, U.S. Department of Energy, Office of Policy, OP-1, 1000 Independence Avenue SW, Washington, DC 20585-0121. Telephone: (202) 586-2859. Email: 
                        <E T="03">FederalRegisterOP@hq.doe.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Due to the receipt of adverse comments, DOE is withdrawing the direct final rule titled “Zero-Based Regulating,” which published on May 29, 2026 (91 FR 
                    <PRTPAGE P="42338"/>
                    31869). DOE stated in that direct final rule that if adverse comments were submitted by June 29, 2026, the direct final rule would not take effect and DOE would publish a timely withdrawal in the 
                    <E T="04">Federal Register</E>
                    . Because DOE subsequently received adverse comments on that direct final rule, DOE withdraws the direct final rule.
                </P>
                <P>DOE published a parallel proposed rule (91 FR 31985, May 29, 2026) on the same day as the direct final rule. The proposed rule invited comments on the substance of the direct final rule. DOE will respond to comments received by June 29, 2026, as part of any final action it takes on the parallel proposed rule.</P>
                <HD SOURCE="HD1">Approval of the Office of the Secretary</HD>
                <P>The Secretary of Energy has approved publication of this notice.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>10 CFR Part 300</CFR>
                    <P>Administrative practice and procedure, Buildings and facilities, Business and industry, Energy conservation, Grant programs—energy, Housing, Reporting and recordkeeping requirements, Technical assistance.</P>
                    <CFR>10 CFR Part 451</CFR>
                    <P>Buildings and facilities, Electric utilities, Energy conservation, Grant programs—energy, Income taxes, Reporting and recordkeeping requirements.</P>
                    <CFR>10 CFR Part 452</CFR>
                    <P>Energy, Grant programs—energy, Reporting and recordkeeping requirements.</P>
                    <CFR>10 CFR Part 602</CFR>
                    <P>Grant programs—health, Medical research, Occupational safety and health, Reporting and recordkeeping requirements.</P>
                    <CFR>10 CFR Part 605</CFR>
                    <P>Accounting, Administrative practice and procedure, Adult education, Aged, Agriculture, American Samoa, Bilingual education, Blind, Business and industry, Civil rights, Colleges and universities, Communications, Community development, Community facilities, Copyright, Credit, Cultural exchange programs, Educational facilities, Educational research, Education, Education of disadvantaged, Education of individuals with disabilities, Educational study programs, Electric power, Electric power rates, Electric utilities, Elementary and secondary education, Energy conservation, Equal educational opportunity, Federally affected areas, Government contracts, Grant programs, Grants administration, Guam, Home improvement, Homeless, Hospitals, Housing, Human research subjects, Indians, Indians—education, Infants and children, Insurance, Intergovernmental relations, International organizations, Inventions and patents, Loan programs, Manpower training programs, Migrant labor, Mortgage insurance, Nonprofit organizations, Northern Mariana Islands, Pacific Islands Trust Territories, Privacy, Renewable Energy, Reporting and recordkeeping requirements, Rural areas, Scholarships and fellowships, School construction, Schools, Science and technology, Securities, Small businesses, State and local governments, Student aid, Teachers, Telecommunications, Telephone, Urban areas, Veterans, Virgin Islands, Vocational education, Vocational rehabilitation, Waste treatment and disposal, Water pollution control, Water resources, Water supply, Watersheds, Women.</P>
                    <CFR>10 CFR Part 706</CFR>
                    <P>Administrative practice and procedure, Labor management relations, Security measures.</P>
                    <CFR>10 CFR Part 708</CFR>
                    <P>Administrative practice and procedure, Whistleblowing.</P>
                    <CFR>10 CFR Part 712</CFR>
                    <P>Administrative practice and procedure, Alcohol abuse, Classified information, Drug abuse, Government contracts, Government employees, Health, Occupational safety and health, Radiation protection, Security measures.</P>
                    <CFR>10 CFR Part 719</CFR>
                    <P>Government contracts, Legal services.</P>
                    <CFR>10 CFR Part 725</CFR>
                    <P>Classified information, Nuclear energy, Reporting and recordkeeping requirements.</P>
                    <CFR>10 CFR Part 727</CFR>
                    <P>Classified information, Computer technology, Government employees, National defense.</P>
                    <CFR>10 CFR Part 733</CFR>
                    <P>Investigations, Reporting and recordkeeping requirements, Science and technology, Scientists.</P>
                    <CFR>10 CFR Part 760</CFR>
                    <P>Public lands-mineral resources, Reporting and recordkeeping requirements, Radioactive materials.</P>
                    <CFR>10 CFR Part 766</CFR>
                    <P>Confidential business information, Electric utilities, Nuclear energy, Radioactive materials, Reporting and recordkeeping requirements, Waste treatment and disposal.</P>
                    <CFR>10 CFR Part 782</CFR>
                    <P>Claims, Copyright, Inventions and patents.</P>
                    <CFR>10 CFR Part 783</CFR>
                    <P>Inventions and patents.</P>
                    <CFR>10 CFR Part 784</CFR>
                    <P>Inventions and patents.</P>
                    <CFR>10 CFR Part 824</CFR>
                    <P>Government contracts, Nuclear energy, Penalties, Security measures.</P>
                    <CFR>10 CFR Part 840</CFR>
                    <P>Administrative practice and procedure, Government contracts, Nuclear energy, Reporting and recordkeeping requirements.</P>
                    <CFR>10 CFR Part 860</CFR>
                    <P>Federal buildings and facilities, Penalties, Security measures.</P>
                    <CFR>10 CFR Part 861</CFR>
                    <P>Federal buildings and facilities, Penalties, Traffic regulations.</P>
                    <CFR>10 CFR Part 862</CFR>
                    <P>Aircraft, Federal buildings and facilities, Security measures.</P>
                    <CFR>10 CFR Part 950</CFR>
                    <P>Government contracts, Radiation protection.</P>
                    <CFR>10 CFR Part 960</CFR>
                    <P>Hazardous waste, Nuclear energy, Radiation protection.</P>
                    <CFR>10 CFR Part 963</CFR>
                    <P>Hazardous waste, Nuclear energy, Radiation protection.</P>
                    <CFR>10 CFR Part 1009</CFR>
                    <P>Fees.</P>
                    <CFR>10 CFR Part 1015</CFR>
                    <P>Administrative practice and procedure, Antitrust, Claims, Fraud, Government employees, Privacy.</P>
                    <CFR>10 CFR Part 1016</CFR>
                    <P>Classified information, Nuclear energy, Reporting and recordkeeping requirements, Security measures.</P>
                    <CFR>10 CFR Part 1045</CFR>
                    <P>Classified information.</P>
                    <CFR>10 CFR Part 1046</CFR>
                    <P>
                        Government contracts, Reporting and recordkeeping requirements, Security measures.
                        <PRTPAGE P="42339"/>
                    </P>
                    <CFR>10 CFR Part 1061</CFR>
                    <P>Administrative practice and procedure.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Signing Authority</HD>
                <P>
                    This document of the Department of Energy was signed on July 06, 2026, by Chris Wright, Secretary of Energy. That document with the original signature and date is maintained by DOE. For administrative purposes only, and in compliance with requirements of the Office of the Federal Register, the undersigned DOE Federal Register Liaison Officer has been authorized to sign and submit the document in electronic format for publication, as an official document of the Department of Energy. This administrative process in no way alters the legal effect of this document upon publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <DATED>Signed in Washington, DC, on July 7, 2026.</DATED>
                    <NAME>Treena V. Garrett,</NAME>
                    <TITLE>Federal Register Liaison Officer, U.S. Department of Energy.</TITLE>
                </SIG>
                <REGTEXT TITLE="10" PART="300">
                    <P>Accordingly, as of July 9, 2026, DOE withdraws the direct final rule amending 10 CFR parts 300, 451, 452, 455, 602, 605, 706, 708, 712, 719, 725, 727, 733, 760, 766, 782, 783, 784, 824, 840, 860, 861, 862, 950, 960, 963, 1009, 1015, 1016, 1045, 1046, and 1061, which published at 91 FR 31869, on May 29, 2026.</P>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13875 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6450-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE</AGENCY>
                <CFR>22 CFR Part 141</CFR>
                <DEPDOC>[Public Notice: 13049]</DEPDOC>
                <RIN>RIN 1400-AG23</RIN>
                <SUBJECT>Rescinding Portions of Department of State Title VI Regulations To Conform More Closely With the Statutory Text and To Implement Executive Order 14281</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of State.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>By this rule, the Department of State (“Department”) amends its regulations implementing Title VI of the Civil Rights Act of 1964 (“Title VI”) to align its regulations with Title VI and, relatedly, to conform to Executive Order 14281.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The rule is effective on July 9, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Heather Olowski, Office of Civil Rights, at 202-647-9295 or email 
                        <E T="03">socr_direct@state.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Executive Summary</HD>
                <P>
                    The Department is rescinding portions of its regulations promulgated pursuant to Title VI, 42 U.S.C. 2000d-1, to more closely align them to the statute, which prohibits only intentionally discriminatory conduct, 
                    <E T="03">see</E>
                     42 U.S.C. 2000d. There are serious statutory and constitutional concerns with the legality of the Department's current Title VI regulations because the current regulations go beyond intentional discrimination to additionally prohibit conduct having an unintentional disparate impact. This rule accordingly deletes those portions of the regulations, which are in considerable tension with the statute and Constitution.
                </P>
                <P>
                    The rule's revisions also conform to Executive Order 14281, 
                    <E T="03">Restoring Equality of Opportunity and Meritocracy,</E>
                     90 FR 17537 (April 28, 2025). That Executive Order states that “[i]t is the policy of the United States to eliminate the use of disparate-impact liability in all contexts to the maximum degree possible to avoid violating the Constitution, Federal civil rights laws, and basic American ideals.” Section 5 of that Executive Order specifically directs the Attorney General to work with Federal agencies, including the Department, to repeal or amend Title VI regulations promulgated under 42 U.S.C. 2000d-1 that address disparate-impact liability. Although the Department would take this action independent of Executive Order 14281, the Order supports this action.
                </P>
                <P>This rule makes clear that the Department's Title VI regulations do not prohibit conduct that has a disparate impact, and the Department thus will not pursue Title VI disparate-impact liability against its Federal-funding recipients.</P>
                <HD SOURCE="HD1">II. Discussion</HD>
                <HD SOURCE="HD2">A. Statutory History of Title VI</HD>
                <P>Title VI of the Civil Rights Act of 1964, as amended, prohibits intentional discrimination on the “ground of race, color, or national origin” in all programs or activities that receive Federal financial assistance. 42 U.S.C. 2000d. Title VI also directs Federal departments and agencies that extend Federal financial assistance to “effectuate the provisions of” Title VI “by issuing rules, regulations, or orders of general applicability.” 42 U.S.C. 2000d-1. The section of Title VI that sets forth the prohibited conduct, 42 U.S.C. 2000d, prohibits only intentional discrimination and makes no reference to unintentional disparate effects or impact. The statute also does not explicitly provide any Federal department or agency with authority to prohibit conduct having an unintentional disparate impact. And no subsequent amendments to the statute have expanded Title VI to encompass disparate-impact liability.</P>
                <HD SOURCE="HD2">B. Regulatory History of Title VI</HD>
                <P>Pursuant to Executive Order 12250, 28 CFR pt. 41, app A, the Department of Justice acts as the lead Federal agency responsible for implementing Title VI's prohibition of discrimination on the basis of race, color, and national origin in programs or activities receiving Federal financial assistance. As part of this responsibility, Executive Order 12250 provides that the Attorney General must approve other agencies' Federal regulations implementing Title VI, including the Department's regulations.</P>
                <P>The Department's Title VI implementing regulations are codified at 22 CFR part 141. The Department originally issued its implementing regulations in 1965. 30 FR 314 (Jan. 9, 1965). In 1973, the Department substantively amended its regulatory description of prohibited discrimination. 38 FR 17946 (July 5, 1973). In 2003, the Department added language regarding “program or activity” to reflect the amendment of Title VI by the Civil Rights Restoration Act of 1987. 68 FR 51334, 51358 (Aug. 26, 2003). Thus, apart from the statutorily required updating of the phrase “program or activity” pursuant to the Civil Rights Restoration Act, the Department has not substantively updated its Title VI regulations since 1973, which was over 50 years ago.</P>
                <P>The Department's implementing regulation describing the scope of prohibited discriminatory conduct, 22 CFR 141.3, currently includes prohibitions on conduct that has an unintentional disparate impact.</P>
                <HD SOURCE="HD2">C. Relevant Supreme Court Decisions</HD>
                <P>
                    The Supreme Court has held that Title VI does not prohibit conduct that has a disparate impact but rather prohibits only intentional discrimination. In 1978, five years after the Department last substantively amended its Title VI regulations, the Supreme Court held that Congress intended Title VI to prohibit “only those racial classifications that would violate the Equal Protection Clause” if committed by a government actor. 
                    <E T="03">Regents of Univ. of Cal.</E>
                     v. 
                    <E T="03">Bakke,</E>
                     438 U.S. 265, 287 (1978) (Powell, J., announcing judgment); 
                    <E T="03">id.</E>
                     at 325, 328, 352 
                    <PRTPAGE P="42340"/>
                    (Brennan, J., joined by White, Marshall, and Blackmun, JJ., concurring in part); 
                    <E T="03">see also Students for Fair Admissions, Inc.</E>
                     v. 
                    <E T="03">President &amp; Fellows of Harvard Coll.,</E>
                     600 U.S. 181, 198 n.2 (2023) (“
                    <E T="03">SFFA”</E>
                    ). Just prior to 
                    <E T="03">Bakke,</E>
                     the Supreme Court held that the Equal Protection Clause prohibits only intentional discrimination, and conduct that has a discriminatory effect or disparate impact alone does not violate that clause. 
                    <E T="03">Washington</E>
                     v. 
                    <E T="03">Davis,</E>
                     426 U.S. 229, 242 (1976); 
                    <E T="03">see also Vill. of Arlington Heights</E>
                     v. 
                    <E T="03">Metro. Hous. Dev. Corp.,</E>
                     429 U.S. 252, 265 (1977) (“Proof of racially discriminatory intent or purpose is required to show a violation of the Equal Protection Clause.”); 
                    <E T="03">Personnel Admin. of Mass.</E>
                     v. 
                    <E T="03">Feeney,</E>
                     442 U.S. 256, 272 (1979) (“[E]ven if a neutral law has a disproportionately adverse effect upon a racial minority, it is unconstitutional under the Equal Protection Clause only if that impact can be traced to a discriminatory purpose.”). Taken together, these Supreme Court cases establish that Title VI's statutory prohibition extends only to intentional discrimination.
                </P>
                <P>
                    In 2001, the Supreme Court, in 
                    <E T="03">Alexander</E>
                     v. 
                    <E T="03">Sandoval,</E>
                     532 U.S. 275 (2001), reaffirmed that Title VI's statutory prohibition on discrimination extends only to intentional discrimination. 
                    <E T="03">Id.</E>
                     at 280-81. In 
                    <E T="03">Sandoval,</E>
                     the Supreme Court held that private plaintiffs could not bring a Title VI action to enforce a then-existing implementing regulation issued by the Department of Justice (“DOJ”), which prohibited conduct that had unintentional discriminatory effects or disparate impacts; this regulation was similar in this regard to the Department's current Title VI regulations. 
                    <E T="03">See id.</E>
                     at 285. Because Title VI prohibits only intentional discrimination, the statutory private cause of action did not extend to the disparate-impact regulations. 
                    <E T="03">Id.</E>
                     at 285-87. Although the Supreme Court in 
                    <E T="03">Sandoval</E>
                     assumed, without deciding, that DOJ's disparate-impact regulation was valid, the Court wrote that the regulation was in “considerable tension” with the Supreme Court's Title VI precedents and that the regulation did not “authoritatively” construe Title VI because it prohibited conduct (
                    <E T="03">i.e.,</E>
                     conduct having an unintentional disparate impact), that Title VI “permits.” 
                    <E T="03">Id.</E>
                     at 281-82, 284-85.
                </P>
                <P>
                    Finally, in 2024, the Supreme Court overruled 
                    <E T="03">Chevron U.S.A. Inc.</E>
                     v. 
                    <E T="03">Natural Resources Defense Council, Inc.,</E>
                     467 U.S. 837 (1984). 
                    <E T="03">See Loper Bright Enters.</E>
                     v. 
                    <E T="03">Raimondo,</E>
                     603 U.S. 369, 409-12 (2024). In doing so, the Supreme Court made clear that “statutes . . . have a single, best meaning” that is “ `fixed at the time of enactment.' ” 
                    <E T="03">Id.</E>
                     at 400 (quoting 
                    <E T="03">Wis. Cent. Ltd.</E>
                     v. 
                    <E T="03">United States,</E>
                     585 U.S. 274, 284 (2018)). Thus, Title VI's bar on discrimination can have only one meaning. And under Supreme Court precedent, the single, best meaning of Title VI is that it “prohibits only intentional discrimination” and “permits” facially neutral policies that result in disparate outcomes so long as there is no discriminatory intent. 
                    <E T="03">Sandoval,</E>
                     532 U.S. at 280, 286 n.6.
                </P>
                <HD SOURCE="HD2">D. Executive Order 14281</HD>
                <P>
                    On April 23, 2025, the President issued Executive Order 14281. This Order restates the “bedrock principle of the United States” “that all citizens are treated equally under the law.” 90 FR at 17537. The Order finds that this “principle guarantees equality of opportunity, not equal outcomes. It promises that people are treated as individuals, not components of a particular race or group.” 
                    <E T="03">Id.</E>
                </P>
                <P>
                    This Order also finds that disparate-impact liability “endangers this foundational principle.” 
                    <E T="03">Id.</E>
                     Disparate-impact liability, the Order reasons, “all but requires individuals and businesses to consider race and engage in racial balancing to avoid potentially crippling legal liability. It not only undermines our national values but also runs contrary to equal protection under the law and, therefore, violates our Constitution.” 
                    <E T="03">Id.</E>
                </P>
                <P>
                    The Order relays that because of these problems, “[i]t is the policy of the United States to eliminate the use of disparate-impact liability in all contexts to the maximum degree possible to avoid violating the Constitution, Federal civil rights laws, and basic American ideals.” 
                    <E T="03">Id.</E>
                     The Order directs the Attorney General to, among other things, review Title VI regulations and “initiate appropriate action to repeal or amend” these regulations “to the extent they contemplate disparate-impact liability.” 
                    <E T="03">Id.</E>
                     Accordingly, this rule revises Department regulations to conform to the direction that the Department coordinate with the Attorney General to repeal and amend the existing regulations as set forth in Section 5 of the Order.
                </P>
                <HD SOURCE="HD2">E. Issues With Current State Department Regulations</HD>
                <P>The Department's regulation at 22 CFR 141.3, entitled “Discrimination prohibited,” contains several provisions that go beyond the text of Title VI and relevant constitutional requirements by prohibiting facially neutral policies that have a disparate impact. Section 143.1(b)(2) is the current regulation's general prohibition of conduct having an unintentional disparate impact; it prohibits certain conduct that has “the effect of subjecting individuals to discrimination,” and it does not mention intent.</P>
                <P>
                    Section 141.3(b)(5) addresses “affirmative action” and provides that funding recipients may intentionally use race to overcome unintentional disparate “effects.” This provision authorizes the intentional use of race, color, or national origin without requiring that the recipient narrowly tailor its use to serve a compelling interest, as is required to satisfy constitutional limits on race-based classifications. 
                    <E T="03">See Adarand Constructors, Inc.</E>
                     v. 
                    <E T="03">Pena,</E>
                     515 U.S. 200, 220 (1995). Similarly, Section 141.3(b)(5) sometimes requires a recipient to intentionally use race, color, or national origin without requiring that such use be narrowly tailored to serve a compelling interest. Finally, Section 141.3(d)(2) addresses prohibited discriminatory employment practices and extends beyond intentional discrimination to prohibiting conduct that “tends” to have a discriminatory effect.
                </P>
                <P>In addition to the serious statutory and constitutional concerns with the legality of the Department's disparate-impact regulations, the Department also has serious policy concerns, including that the disparate-impact standard creates confusion, undermines public confidence in the nation's civil rights laws and the rule of law, and produces burdensome litigation and compliance costs.</P>
                <HD SOURCE="HD3">1. Serious Legal Concerns</HD>
                <P>
                    There are serious statutory concerns as to whether Title VI authorizes the disparate-impact provisions of the current regulations. 
                    <E T="03">Sandoval</E>
                     and 
                    <E T="03">Loper Bright</E>
                     call their legality into serious doubt. Title VI authorizes agencies to promulgate regulations “to effectuate” the statute's prohibition of intentional discrimination. 42 U.S.C. 2000d-1. The current regulations' prohibition of conduct having an unintentional disparate impact expands the regulation to prohibit a vastly broader scope of conduct than the statute itself prohibits. This scope is too broad to be considered a simple prophylactic measure aimed at preventing intentional discrimination.
                </P>
                <P>
                    There are also serious concerns about whether the Department's Title VI regulations pass constitutional muster under the Equal Protection Clause. As the Supreme Court recently held in 
                    <E T="03">SFFA,</E>
                     “the Equal Protection Clause . . . applies without regard to any 
                    <PRTPAGE P="42341"/>
                    differences of race, of color, or of nationality—it is universal in its application,” and the “guarantee of equal protection cannot mean one thing when applied to one individual and something else when applied to a person of another color.” 600 U.S. at 206 (internal quotation marks omitted) (first quoting 
                    <E T="03">Yick Wo</E>
                     v. 
                    <E T="03">Hopkins,</E>
                     118 U.S. 356, 369 (1886); and then quoting 
                    <E T="03">Bakke,</E>
                     438 U.S. at 289-90 (Powell, J.)). Here, however, the funding recipient's risk of disparate-impact liability is triggered by unintentional disparate outcomes, which a recipient may not even know about without investigation. To evaluate and avoid this risk, the funding recipient must incur investigatory costs, such as conducting an impact analysis, and proactively consider race and potentially use it to change unintended disparate outcomes.
                </P>
                <P>
                    Disparate-impact liability thus encourages and, in some cases, requires covered entities to engage in the intentional use of race and racial balancing to eliminate those disparate outcomes. This encouraged or coerced use of race violates the Equal Protection Clause unless it satisfies strict scrutiny. 
                    <E T="03">See SFFA,</E>
                     600 U.S. at 206-07. Similarly, the “affirmative action” provision authorizes and sometimes requires the intentional use of race without requiring that this intentional use be narrowly tailored to serve a recognized compelling interest. Instead, it encourages intentional racial balancing.
                </P>
                <P>This equal protection problem also further calls into doubt the proposition that Title VI authorizes disparate-impact liability, as it presents a conflict between the regulation and the statute. The statute forbids intentional racial balancing, while the regulation requires or encourages it, creating a conflict between the two. This conflict not only produces confusion and tends to undermine public confidence in the law but also shows that the Department has deviated too far from its authority to effectuate the statute.</P>
                <P>
                    As summarized above, there are serious statutory and constitutional concerns with the legality of the Department's Title VI disparate-impact regulations. But even if the regulations are legal, the Department finds that eliminating the concerns addressed above and the costs and confusion caused by the conflict between the statute and the regulations also justifies the repeal of the regulations. 
                    <E T="03">Cf. U.S. Tel. Ass'n</E>
                     v. 
                    <E T="03">FCC,</E>
                     188 F.3d 521, 528 (D.C. Cir. 1999) (concluding it was not “arbitrary and capricious” to adopt a certain policy in order to “avoid[ ] raising a non-trivial constitutional question”).
                </P>
                <HD SOURCE="HD3">2. Serious Policy Concerns</HD>
                <P>
                    The Department also has serious policy concerns with the imposition of disparate-impact liability. Executive Order 14281 explains many of the valid policy concerns associated with disparate-impact liability. 90 FR at 17537. Moreover, the legal concerns described above have caused uncertainty and confusion for Federal-funding recipients as to whether and when they need to comply with the disparate-impact regulations and when they can or must consider race. As explained above, 
                    <E T="03">Sandoval</E>
                     has created uncertainty as to the validity of the disparate-impact regulations that many Federal departments and agencies have promulgated.
                </P>
                <P>Additionally, in practice, as above, disparate-impact liability leads covered entities to engage in racial balancing even as Title VI forbids racial balancing. This tension tends to create confusion and undermine public confidence in the nation's civil rights laws and in the rule of law itself, as the law seems to both forbid and require the same conduct. These problems are amplified by the arbitrary nature of the racial and ethnic categories typically used to measure disparate effects, which, by virtue of their arbitrariness, typically lack a meaningful connection to a compelling interest.</P>
                <P>This confusion and the weakening of the nation's civil rights laws' ability to teach principles of nondiscrimination is evident in, among other things, many grant proposals for which the U.S. government awarded funds in past years that explicitly targeted certain racial groups. The Department believes these policy concerns justify repealing certain parts of its regulation to cure this confusion, to remove the incentive for covered entities to engage in racial balancing, and to maintain clarity and public confidence in the nation's civil rights laws.</P>
                <P>The Department has considered that an evaluation of disparate effects can sometimes be useful in uncovering or deterring subtle discrimination or indifference to unnecessary and arbitrary barriers. Eliminating disparate-impact liability, however, does not preclude the use of data on disparate outcomes to help prove intentional discrimination. Both the Department and private litigants rely on such data, as an evidentiary matter, to help prove intentional discrimination.</P>
                <P>The Department has also considered the alternative of trying to adopt a narrower version of disparate-impact liability. One way to adopt a narrower version of liability would be to increase the statistical threshold required for disparate-impact claims. But this would not eliminate the Department's serious legal and policy concerns with disparate-impact liability. Even if possible, developing such a rule would not solve the confusion or rule-of-law concerns expressed above or reduce the compliance and litigation costs that covered entities face. The Department believes that the better course is to avoid the complexities and litigation associated with this alternative, which ultimately would leave some of the problems unaddressed and others inadequately addressed.</P>
                <P>
                    The Department also considered the potential reliance interests of funding recipients and others. 
                    <E T="03">Sandoval,</E>
                     however, cast serious doubt on the regulations more than 20 years ago. At least since then, the Department's enforcement of its disparate-impact regulations has been virtually nonexistent. And Executive Order 14281 also directed all agencies to “deprioritize enforcement of all statutes and regulations to the extent they include disparate-impact liability,” including specifically the Department's Title VI disparate-impact regulations. The Department accordingly believes that any reliance interests should be minimal, and, regardless, that they do not outweigh the Department's legal and other policy concerns.
                </P>
                <P>
                    The Department notes that 
                    <E T="03">Sandoval</E>
                     has also led to a divergence between Title VI enforcement by private plaintiffs and enforcement by Federal departments and agencies. After 
                    <E T="03">Sandoval,</E>
                     private plaintiffs can enforce only Title VI's statutory prohibition on intentional discrimination. Repealing the Department's disparate-impact regulations would eliminate this incongruent enforcement.
                </P>
                <P>Overall, the Department finds that, regardless of the legality of the regulations, the above-summarized policy concerns justify the repeal of its disparate-impact regulations.</P>
                <HD SOURCE="HD1">III. Changes</HD>
                <P>
                    This rule's regulatory changes address the concerns that the Supreme Court raised in 
                    <E T="03">Sandoval</E>
                     and the other legal and policy concerns discussed above, harmonize the implementing regulations with Title VI, promote consistent enforcement among private plaintiffs and Federal departments and agencies, and provide much needed clarity to the courts and Federal-funding recipients and beneficiaries.
                </P>
                <P>
                    For the reasons summarized above, the Department amends the following 
                    <PRTPAGE P="42342"/>
                    provisions in its Title VI implementing regulation that explain the particular types of “Discrimination prohibited,” located at 22 CFR 141.3.
                </P>
                <HD SOURCE="HD2">A. Table Summarizing Changes</HD>
                <P>The table below indicates the exact wording changes. For each section indicated in the left column, the text shown in the middle column is removed and the text shown in the right column is added:</P>
                <GPOTABLE COLS="3" OPTS="L2,nj,tp0,i1" CDEF="s50,r100,r200">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Section</CHED>
                        <CHED H="1">Remove</CHED>
                        <CHED H="1">Add</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">141.3(b)(2)</ENT>
                        <ENT>Full text of paragraph: “(2) A recipient . . . or national origin.”</ENT>
                        <ENT>Replace removed text with “In determining the site or location of facilities, a recipient or applicant may not make selections with the purpose of excluding individuals from, denying them the benefits of, or subjecting them to discrimination under any program to which this subpart applies, on the ground of race, color, or national origin; or with the purpose of defeating or substantially impairing the accomplishment of the objectives of the Act or this subpart.”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">141.3(b)(5)</ENT>
                        <ENT>Full text of paragraph (including both subparagraphs i and ii)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">141.3(d)(2)</ENT>
                        <ENT>Full text of paragraph</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">B. Section-by-Section Analysis</HD>
                <HD SOURCE="HD3">Section 141.3(b)(2)</HD>
                <P>Section 141.3(b)(2) is the general prohibition of conduct having an unintentional disparate impact. It imposes liability on Federal-funding recipients who “utilize criteria or methods of administration which have the effect of subjecting individuals to discrimination.” Because section 141.3(b)(2)'s only purpose is to prohibit disparate-impact discrimination, this rule deletes this paragraph in its entirety. It thus amends the regulations to conform to Title VI and to address the legal and policy considerations and determinations described in this document. The rule replaces paragraph (b)(2) with regulatory language to make clear that intentional discrimination is prohibited in the selection of the site or location of facilities.</P>
                <HD SOURCE="HD3">Section 141.3(b)(5)</HD>
                <P>Section 141.3(b)(5) deals with “affirmative action.” Paragraph (b)(5)(ii) authorizes affirmative action in programs even in the absence of a finding of prior discrimination in a program “to overcome the effects of conditions which resulted in limiting participation by persons of a particular race, color, or national origin.” This provision points not to intentional discrimination but rather to the unintentional “effects of conditions.” The provision consequently authorizes intentional racial classifications, racial preferences, and other race-based actions without the supporting compelling interest and narrow tailoring that the Equal Protection Clause demands. This section has long been unlawful in light of the Equal Protection Clause.</P>
                <P>
                    Paragraph (b)(5)(i) 
                    <E T="03">requires</E>
                     that a recipient “must take affirmative action to overcome the effects of prior discrimination” if in “administering a program” the “recipient has previously discriminated.” This provision problematically goes well beyond the Equal Protection Clause, which permits in limited circumstances, but does not mandate, a government to take narrowly tailored action to remedy the effects of its particular past discrimination. Moreover, even putting aside the mandatory language, this provision does not require sufficient narrow tailoring to particular past discrimination, but rather simply “affirmative action to overcome the effects of prior discrimination.” This provision accordingly promotes potential illegal race discrimination because of a lack of tailoring. Moreover, it problematically requires recipients to consider and use racial preferences when the recipient may not want to consider or use racial preferences. This is contrary to the Department's goal of promoting and defending a culture of nondiscrimination and is destructive of the public's understanding of and faith in the nation's civil rights laws. The Department no longer mandate or authorize this use of race, and this rule therefore deletes paragraph (b)(5) in its entirety.
                </P>
                <HD SOURCE="HD3">Section 141.3(d)(2)</HD>
                <P>Section 141.3(d) addresses prohibited discriminatory employment practices. Paragraph (d)(1) prohibits intentionally discriminatory employment practices when a primary objective of the Federal financial assistance is to provide employment. Paragraph (d)(2) extends the prohibition to employment practices of the recipient from Paragraph (d)(1) even when the “primary objective of the financial assistance is not to provide employment” if discrimination in the non-funded “employment practices . . . tends, on the ground of race, color, or national origin, to exclude individuals from participation in, to deny them the benefits of, or to subject them to discrimination under the program to which this regulation applies . . . .” This paragraph prohibits not only intentional discrimination but rather extends to conduct that “tends” to have a discriminatory effect on a program without the primary objective of providing employment.</P>
                <P>
                    Moreover, paragraph (d)(2)'s extension to employment practices where the Federal funding's primary objective is not to provide employment conflicts with the limitation on Title VI found in 42 U.S.C. 2000d-3. Section 2000d-3 states that “[n]othing contained in [Title VI] shall be construed to authorize action under [Title VI] by any department or agency with respect to any employment practice of any employer, employment agency, or labor organization except where a primary objective of the Federal financial assistance is to provide employment.” 
                    <E T="03">Id.; see also Johnson</E>
                     v. 
                    <E T="03">Transp. Agency, Santa Clara Cnty.</E>
                     480 U.S. 616, 628 n.6 (1987) (citing the statutory limitation and noting Congress's intent that Title VI not “impinge” on Title VII, which prohibits discriminatory employment practices). The rule deletes paragraph (d)(2) to amend the regulation so that it more closely adheres to Title VI. This rule makes no change to the current text of paragraph (d)(1).
                </P>
                <HD SOURCE="HD1">IV. Severability</HD>
                <P>
                    The Department's position is that each of the amendments described in this rule serves a vital, related, but distinct purpose. The Department also confirms that each of the amendments is intended to operate independently of each other and that the potential invalidity of one amendment should not affect the other amendments. The Department would adopt any of the amendments independently of the invalidity of a separate amendment.
                    <PRTPAGE P="42343"/>
                </P>
                <HD SOURCE="HD1">V. Regulatory Analysis</HD>
                <HD SOURCE="HD2">A. Administrative Procedure Act</HD>
                <P>The Department issues this final rule without prior public notice and comment pursuant to the Administrative Procedure Act's exception for rules “relating to agency management or personnel or to public property, loans, grants, benefits, or contracts.” 5 U.S.C. 553(a)(2). This rule falls into that exception.</P>
                <P>
                    Title VI concerns non-discrimination conditions on the receipt of Federal financial assistance, and more particularly to the receipt of Federal “[g]rants and loans,” “property,” “personnel” and “[a]ny Federal agreement, arrangement, or other contract which has as one of its purposes the provision of assistance.” 22 CFR 141.12(e); 
                    <E T="03">see also</E>
                     22 CFR 141.4 (requiring funding recipient sign contractual assurance of compliance with Title VI). 
                    <E T="03">Cf. Education Programs or Activities Receiving or Benefitting From Federal Financial Assistance,</E>
                     82 FR 46655 (Oct. 6, 2017) (invoking exception to amend Title IX regulations to “promote consistency in the enforcement of Title IX for [Department of Agriculture] financial assistance recipients”); 
                    <E T="03">Preserving Community and Neighborhood Choice,</E>
                     85 FR 47899 (Aug. 7, 2020) (invoking exception to repeal Housing and Urban Development rule regarding Federal grantees); 
                    <E T="03">Participation by Minority Business Enterprise in Department of Transportation Programs,</E>
                     53 FR 18285 (May 23, 1988) (invoking exception to expand coverage of Department of Transportation regulation regarding Federal Aviation Administration's airport financial assistance program); 
                    <E T="03">Nondiscrimination on the Basis of Handicap in Federally Assisted Programs: Suspension of Guidelines With Respect to Mass Transportation,</E>
                     46 FR 40687 (Aug. 11, 1981) (invoking exception to suspend Department of Justice guidelines regarding prohibiting disability discrimination in transportation programs and activities receiving Federal financial assistance).
                </P>
                <P>
                    Indeed, invoking 5 U.S.C. 553(a)(2) is consistent with guidance issued by the Office of Management and Budget (“OMB”), 
                    <E T="03">see</E>
                     2 CFR 200.1, which defines “Federal financial assistance” with the same categories as the Administrative Procedure Act's exception for rules “relating to agency management or personnel or to public property, loans, grants, benefits, or contracts,” 5 U.S.C. 553(a)(2). With potentially limited exceptions not applicable to the Department, all the forms of Federal financial assistance set forth under 2 CFR 200.1 that the Department administers would fall under the exception for “public property, loans, grants, benefits, or contracts.” Thus, the Department issues this final rule without prior public notice and comment under 5 U.S.C. 553(a)(2) and without a delayed effective date under 5 U.S.C. 553(d).
                </P>
                <HD SOURCE="HD2">B. Executive Orders 12866 and 13563 (Regulatory Review)</HD>
                <P>The Office of Information and Regulatory Affairs (“OIRA”) has determined that this rulemaking is a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, but it is not an “economically significant” action under section 3(f)(1). Accordingly, this rule has been submitted to the Office of Management and Budget (“OMB”) for review.</P>
                <P>
                    This regulation has been drafted and reviewed in accordance with Executive Order 12866, 
                    <E T="03">Regulatory Planning and Review,</E>
                     section 1(b), Principles of Regulation, and in accordance with Executive Order 13563, 
                    <E T="03">Improving Regulation and Regulatory Review,</E>
                     section 1(b), General Principles of Regulation, which supplements and reaffirms the principles of Executive Order 12866. These Executive Orders direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits. Executive Order 13563 also recognizes that some benefits and costs are difficult to quantify and provides that, where appropriate and permitted by law, agencies may consider and discuss qualitatively values that are difficult or impossible to quantify.
                </P>
                <P>
                    As explained in the preamble, the regulatory modifications this rule makes are necessary to conform Department regulations to Executive Order 14281, to address serious legal concerns regarding the Department's Title VI regulation based on the Supreme Court's reading of Title VI in 
                    <E T="03">Sandoval,</E>
                     harmonize the implementing regulation's scope with Title VI, promote consistency in enforcement among private plaintiffs and Federal departments and agencies, and provide much needed clarity to courts and Federal-funding recipients and beneficiaries regarding the scope of the Department's Title VI regulations. Indeed, with respect to section 141.3(b)(5) of the Department's Title VI implementing regulations, the changes this rule makes are clearly necessary to bring the regulations into compliance with the Equal Protection Clause. In short, this rule is necessary to conform the Department's regulation to existing law, as interpreted by the Supreme Court.
                </P>
                <P>Data limitations make the costs and benefits of the rule difficult to quantify. Although it does not represent the monetary impact of the rule, the Department issued approximately 66,665 separate awards totaling approximately $44.64 billion over the past four years. In Fiscal Year 2024 alone, the Department issued approximately 15,795 separate awards totaling $14.01 billion. In the past, the Department did not record data regarding the applicability of Title VI, and these total figures include foreign recipients outside the United States who may not be subject to Title VI requirements. Further, with respect to discrimination and unintentional disparate-impact liability, the Department does not track and cannot reliably quantify the costs attributable to the varying disparate-impact portions of the financial assistance it has awarded. That disparate impact is sometimes a factor that may be considered in determining whether discrimination was intentional further impedes monetizing costs and benefits. Therefore, the overall cost effect on the Department is difficult to quantify, but the deregulatory action should decrease the Department's compliance costs, while also providing a benefit (also difficult to quantify) of bringing the Department's conduct in line with the law. Similarly, the Department is unable to quantify how funding recipients will respond to the regulatory changes, but the deregulatory action should result in greater flexibility and lower compliance costs for recipients.</P>
                <P>
                    The Department recognizes that a funding recipient may receive Federal funds from sources other than the Department. Regardless, the Department does not envision that this rule will appreciably increase administrative or compliance costs for funding recipients who must also adhere to the regulations of another department or agency. This deregulatory action does not create any new obligations for funding recipients. On the contrary, by eliminating disparate-impact liability from the regulation, the rule eliminates a source of regulatory confusion, narrows the conduct prohibited, and thus lessens the costs of compliance and potential liability. Moreover, recipients who receive funds for the same program or activity from more than one Federal entity already enter into separate contractual assurances with each funding entity. 
                    <E T="03">See, e.g.,</E>
                     22 CFR 141.4. These contractual assurances already impose varying requirements that each 
                    <PRTPAGE P="42344"/>
                    Federal funding source deems necessary. Funding recipients will continue to be held to the most stringent contractual assurance and regulation. And in any event, the Department notes that other agencies are currently amending their regulations to align with the changes made in this rule, so the Department anticipates that there will be little, if any, disparity in federal requirements regarding disparate-impact liability going forward.
                </P>
                <P>Based on the analysis of the practical qualitative costs and benefits noted above, the Department believes that this rule is consistent with the principles of Executive Orders 12866 and 13563, including the requirements that, to the extent permitted by law, the Department adopt a regulation only upon a reasoned determination that its benefits justify its costs and choose a regulatory approach that maximizes net benefits.</P>
                <P>The Department has determined that this rule is a “significant regulatory action” under Executive Order 12866, section 3(f), and OMB has accordingly reviewed this rule.</P>
                <HD SOURCE="HD2">C. Executive Order 14192 (Unleashing Prosperity Through Deregulation)</HD>
                <P>Executive Order 14192 (Unleashing Prosperity through Deregulation) requires an agency, unless prohibited by law, to identify at least 10 existing regulations to be repealed when the agency publicly proposes for notice and comment or otherwise promulgates a new regulation. In furtherance of this requirement, section 3(c) of the Order requires that the new incremental costs associated with new regulations shall, to the extent permitted by law, be offset by the elimination of existing costs associated with at least 10 prior regulations. This rule eliminates unnecessary regulation by revising the Department's current Title VI regulations, which extend prohibited conduct to include conduct having an unintentional disparate impact and thus expand the scope of those regulations to a vastly broader range of conduct than the statute prohibits. Accordingly, the Department expects this rule to be a deregulatory action under Executive Order 14192.</P>
                <HD SOURCE="HD2">D. Executive Order 14294 (Overcriminalization of Federal Regulations)</HD>
                <P>
                    Executive Order 14294 requires agencies promulgating regulations with criminal regulatory offenses potentially subject to criminal enforcement to explicitly describe the conduct subject to criminal enforcement, the authorizing statutes, and the 
                    <E T="03">mens rea</E>
                     standard applicable to each element of those offenses. This rule does not impose a criminal regulatory penalty and is thus exempt from Executive Order 14924 requirements.
                </P>
                <HD SOURCE="HD2">E. Executive Order 13132 (Federalism)</HD>
                <P>This rule will not have a substantial, direct effect on the relationship between the national government and the states, on distribution of power and responsibilities among various levels of government, or on states' policymaking discretion. States that choose to receive Title VI funding from the Department do so voluntarily and agree to comply with relevant statutory requirements as a condition of receiving such funding. This rule does not subject states or any other funding recipients or beneficiaries to new obligations. This rule amends and clarifies existing regulations that are required by statute. Therefore, in accordance with Section 6 of Executive Order 13132, the Department has determined that these amendments do not have sufficient federalism implications to warrant the preparation of a federalism summary impact statement.</P>
                <HD SOURCE="HD2">F. Executive Order 12988 (Civil Justice Reform; Plain Language)</HD>
                <P>This rule meets the applicable standards set forth in sections 3(a) and (b)(2) of Executive Order 12988 to specify provisions in clear language. Pursuant to section 3(b)(1)(I) of the Executive Order, nothing in this proposed or any previous rule (or in any administrative policy, directive, ruling, notice, guideline, guidance, or writing) directly relating to the program that is the subject of this proposed rule is intended to create any legal or procedural rights enforceable against the United States.</P>
                <HD SOURCE="HD2">G. Executive Order 12250, “Leadership and Coordination of Nondiscrimination Laws”</HD>
                <P>
                    Pursuant to section 1-202 of Executive Order 12250, DOJ has the responsibility to “review . . . proposed rules . . . of the Executive agencies” implementing nondiscrimination statutes such as Title VI in order to identify those which are inadequate, unclear or unnecessarily inconsistent.” Additionally, section 1-101 of Executive Order 12250 delegated the President's responsibility to approve Title VI regulations to the Attorney General. 
                    <E T="03">See</E>
                     42 U.S.C. 2000d-1. DOJ has reviewed and approved this rule.
                </P>
                <HD SOURCE="HD2">H. Regulatory Flexibility Act</HD>
                <P>
                    The Department, in accordance with the Regulatory Flexibility Act (“RFA”), 5 U.S.C. 605(b), has reviewed these regulations and certifies that the rule's changes will not have a significant economic impact on a substantial number of small entities, in large part because these regulatory changes do not impose any new substantive obligations on Federal-funding recipients. The rule amends and clarifies existing regulations that are required by Title VI. The rule merely brings the Department into compliance with the Equal Protection Clause and harmonizes the scope of its regulations to conform with the scope of Title VI, which does not prohibit conduct having an unintentional disparate impact. All Federal-funding recipients have been bound by the existing standards that will remain in place after this rule since their initial promulgation. This rule also does not require a regulatory flexibility analysis under the RFA, 5 U.S.C. 603, 604, because, for the reasons described above, no notice of proposed rulemaking is required under 5 U.S.C. 553. 
                    <E T="03">See Or. Trollers Ass'n</E>
                     v. 
                    <E T="03">Gutierrez,</E>
                     452 F.3d 1104, 1123-24 (9th Cir. 2006) (noting that the RFA does not apply when an agency validly invokes an exception to the public comment requirements of 5 U.S.C. 553).
                </P>
                <HD SOURCE="HD2">I. Unfunded Mandates Reform Act of 1993</HD>
                <P>The Unfunded Mandates Reform Act of 1995 (“UMRA”), 15 U.S.C. 1532, requires agencies to prepare several analytic statements before proposing any rule that may result in annual expenditures of $100 million by state, local, tribal governments, or the private sector. Section 4(2) of the UMRA, however, excludes from the Act's coverage any proposed or final Federal regulation that “establishes or enforces any statutory rights that prohibit discrimination on the basis of race, color, religion, sex, national origin, age, handicap, or disability.” Accordingly, this rulemaking is not subject to the provisions of the UMRA.</P>
                <HD SOURCE="HD2">J. Congressional Review Act</HD>
                <P>OIRA has determined that this rule is not a “major rule” as defined by the Congressional Review Act, 5 U.S.C. 804(2).</P>
                <HD SOURCE="HD2">K. Paperwork Reduction Act</HD>
                <P>
                    This rule will not impose additional reporting or recordkeeping requirements under the Paperwork Reduction Act of 1995, 44 U.S.C. 3501, 
                    <E T="03">et seq.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects for 22 CFR Part 141</HD>
                    <P>Administrative practice and procedure, Civil rights, Equal employment opportunity, Grant programs.</P>
                </LSTSUB>
                <PRTPAGE P="42345"/>
                <P>Accordingly, for the reasons set forth above, part 141 of title 22 of the Code of Federal Regulations is amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 141—NONDISCRIMINATION IN FEDERALLY-ASSISTED PROGRAMS OF THE DEPARTMENT OF STATE—EFFECTUATION OF TITLE VI OF THE CIVIL RIGHTS ACT OF 1964</HD>
                </PART>
                <REGTEXT TITLE="22" PART="141">
                    <AMDPAR>1. The authority citation for part 141 is revised to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 42 U.S.C. 2000d, 2000d-7; E.O. 12250, 45 FR 72995, 3 CFR, 1980 Comp., p. 298; E.O. 14281, 90 FR 17537.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="22" PART="141">
                    <AMDPAR>2. In § 141.3:</AMDPAR>
                    <AMDPAR>a. Revise paragraph (b)(2);</AMDPAR>
                    <AMDPAR>b. Remove paragraph (b)(5); and</AMDPAR>
                    <AMDPAR>c. Remove and reserve paragraph (d)(2).</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 141.3 </SECTNO>
                        <SUBJECT>Discrimination prohibited.</SUBJECT>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>(2) In determining the site or location of facilities, a recipient or applicant may not make selections with the purpose of excluding individuals from, denying them the benefits of, or subjecting them to discrimination under any program to which this subpart applies, on the ground of race, color, or national origin; or with the purpose of defeating or substantially impairing the accomplishment of the objectives of the Act or this part.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>Michael J. Rigas,</NAME>
                    <TITLE>Deputy Secretary for Management and Resources, U.S. Department of State.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13860 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4710-10-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <CFR>26 CFR Part 1</CFR>
                <DEPDOC>[TD 10052]</DEPDOC>
                <RIN>RIN 1545-BQ07</RIN>
                <SUBJECT>Information Reporting and Transfer for Valuable Consideration Rules for Section 1035 Exchanges of Life Insurance and Certain Other Life Insurance Contract Transactions</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document contains final regulations providing guidance on the application of the transfer for valuable consideration rules and associated information reporting requirements for reportable policy sales of interests in life insurance contracts to exchanges of life insurance contracts qualifying for nonrecognition of gain or loss and certain acquisitions of interests in life insurance contracts in transactions that qualify as corporate reorganizations. The final regulations affect parties involved in these life insurance contract transactions, including with respect to payments of reportable death benefits.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>
                        <E T="03">Effective date:</E>
                         These regulations are effective on July 9, 2026.
                    </P>
                    <P>
                        <E T="03">Applicability dates:</E>
                         For dates of applicability, 
                        <E T="03">see</E>
                         §§ 1.101-6 and 1.6050Y-1(b).
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Allan H. Sakaue, (202) 317-6995 (not a toll-free number).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Authority</HD>
                <P>This document contains amendments to 26 CFR part 1 under sections 101 and 6050Y of the Internal Revenue Code (Code) issued pursuant to the express delegations of authority to the Secretary of the Treasury or his delegate (Secretary) provided under sections 6050Y(a) through (c), and 7805(a) of the Code (final regulations).</P>
                <P>Section 6050Y provides express delegations of authority to the Secretary to prescribe the time and manner to file information returns and furnish statements setting forth certain information specified therein by the following persons: (1) an acquirer of a life insurance contract or any interest in a life insurance contract in a reportable policy sale during any taxable year (section 6050Y(a)); (2) an issuer of a life insurance contract in connection with a reportable policy sale (section 6050Y(b)); and (3) a payor of death benefits during any taxable year under a life insurance contract transferred in a reportable policy sale (section 6050Y(c)).</P>
                <P>Section 7805(a) authorizes the Secretary to “prescribe all needful rules and regulations for the enforcement of [the Code], including all rules and regulations as may be necessary by reason of any alteration of law in relation to internal revenue.”</P>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    These final regulations amend regulations under sections 101 and 6050Y published in the 
                    <E T="04">Federal Register</E>
                     (TD 9879, 84 FR 58460) on October 31, 2019, as corrected (84 FR 68042) on December 13, 2019 (2019 final regulations).
                </P>
                <P>
                    The Department of the Treasury (Treasury Department) and the IRS published proposed regulations under sections 101 and 6050Y (REG-108054-21) in the 
                    <E T="04">Federal Register</E>
                     (88 FR 30058) on May 10, 2023 (2023 proposed regulations). The 2023 proposed regulations were published in response to concerns raised following publication of the 2019 final regulations regarding the application of sections 101 and 6050Y to exchanges to which section 1035 of the Code applies (section 1035 exchanges) and to transfers of contracts occurring in corporate reorganizations under section 368 of the Code. The Treasury Department and the IRS received written comments on the 2023 proposed regulations and held a public hearing on September 28, 2023.
                </P>
                <P>After consideration of the written comments and comments received at the hearing, this Treasury Decision adopts the 2023 proposed regulations as final regulations with modifications, as described in the Summary of Comments and Explanation of Revisions.</P>
                <HD SOURCE="HD1">Summary of Comments and Explanation of Revisions</HD>
                <P>This Summary of Comments and Explanation of Revisions section discusses the comments received on the 2023 proposed regulations and explains the revisions adopted in the final regulations in response to those comments.</P>
                <HD SOURCE="HD2">1. Comments Relating to Section 1035 Exchanges</HD>
                <P>
                    As described in the preamble to the 2023 proposed regulations, the proposed changes relating to section 1035 exchanges are intended to correct an unintended change effected by the 2019 final regulations to the treatment under section 101 of a life insurance contract issued to a policyholder in a section 1035 exchange, while continuing to address the concerns that prompted the inclusion of rules for section 1035 exchanges in the 2019 final regulations. These concerns include: (1) that the reporting of death benefits paid under section 6050Y(c) could be avoided by exchanging a contract transferred in a reportable policy sale (reportable policy sale (RPS) contract) for a new contract in a section 1035 exchange and (2) that a policyholder could attempt to avoid the limitation on the excludability of death benefits resulting from the application of the “transfer for value” rule set forth in section 101(a)(2) through a section 1035 exchange. The 2023 proposed regulations would accomplish these objectives in four ways: (1) by removing the reference to section 1035 exchanges in the definition of a “transfer of an interest in a life insurance contract” 
                    <PRTPAGE P="42346"/>
                    (§ 1.101-1(e)(2) of the 2023 proposed regulations); (2) by adding a new rule on how to determine the amount of the proceeds attributable to an interest in a life insurance contract issued in a section 1035 exchange that is excludable from gross income under section 101(a) (§ 1.101-1(b)(2)(iv) of the 2023 proposed regulations); (3) by modifying the definition of “reportable policy sale” to address section 1035 exchanges (§ 1.101-1(c)(3) of the 2023 proposed regulations); and (4) by making conforming modifications to §§ 1.6050Y-1 through 1.6050Y-4 of the 2019 final regulations. Regarding conforming modifications to the reporting requirements under section 6050Y, because section 1035 exchanges of RPS contracts would no longer be required to be reported under §  1.6050Y-2 of the 2019 final regulations, the 2023 proposed regulations would modify the reporting rules under §§  1.6050Y-3 and 1.6050Y-4 of the 2019 final regulations to ensure proper reporting of reportable death benefits paid under contracts issued in section 1035 exchanges.
                </P>
                <P>Commenters generally expressed support for the 2023 proposed regulations under section 101 regarding the treatment of section 1035 exchanges. However, two commenters requested clarification of certain issues related to these provisions. Additionally, one commenter requested changes to the 2023 proposed regulations under section 6050Y related to tracking and information reporting requirements for section 1035 exchanges of contracts that have been transferred in reportable policy sales.</P>
                <P>These comments are addressed in detail in parts 1.A through 1.D of this Summary of Comments and Explanation of Revisions.</P>
                <HD SOURCE="HD3">A. Comments Supporting the 2023 Proposed Regulations</HD>
                <P>Comments supporting the 2023 proposed regulations under section 101 regarding the treatment of section 1035 exchanges included comments from a commenter that agreed with the determination in the 2023 proposed regulations to exclude the issuance of a life insurance contract to a policyholder, without qualification, from the events treated as a transfer of an interest in a life insurance contract. The commenter specifically supported the proposed modification of § 1.101-1(e)(2) of the 2019 final regulations to delete the phrase “other than the issuance of a policy in an exchange pursuant to section 1035” from the last clause of that section. The commenter noted that it is well understood that a section 1035 exchange does not transfer the beneficial rights of life insurance coverage to a different policyholder/beneficiary, but, rather, is an exchange of an existing life insurance coverage for new life insurance coverage without any material change. The commenter also stated that it is well-settled in past IRS rulings that a section 1035 exchange does not change the tax attributes of the relinquished contract. Accordingly, the commenter reasoned, when an RPS contract is relinquished in a section 1035 exchange, the contract received in exchange should be treated as an RPS contract.</P>
                <P>Another commenter agreed that the 2023 proposed regulations correctly conclude that a section 1035 exchange, in and of itself, is not a “transfer” of the newly issued contract received in the exchange. In support of the approach adopted in the 2023 proposed regulations, the commenter observed that issuing a contract is not a “transfer,” as a transfer of property presupposes the existence of property that can be transferred, and the new contract received in a section 1035 exchange does not exist until it is issued. The commenter also explained that the 2019 final regulations create a conundrum by treating all section 1035 exchanges as transfers for valuable consideration for which the carryover basis exception is never available to undo that treatment, regardless of whether the policyholder has a substantial relationship with the insured when the exchange occurs. The commenter remarked that, if left uncorrected, the 2019 final regulations would effect a major change in the Federal income tax treatment of contract exchanges, as section 1035 exchanges never triggered the transfer for value rule before the 2019 final regulations. The commenter applauded the Treasury Department and the IRS for recognizing that such a change in law is not warranted or appropriate, for announcing a correction in the 2023 proposed regulations, and for extending the correction retroactively to eliminate any doubt for taxpayers regarding the Federal income tax treatment of contract exchanges they may have completed in prior years. In further support of the 2023 proposed regulations, the commenter also noted that the regulations should not subvert the intent of section 1035, which is to ensure that policyholders are able to exchange existing life insurance contracts for new ones better suited to their needs without having to recognize gain, and that the 2019 final regulations inappropriately subvert the intent of section 1035 by applying the transfer for value rule merely because a life insurance contract is exchanged for a new one. The commenter further expressed agreement with the preamble to the 2023 proposed regulations that the provisions therein are not inconsistent with section 101(j), which concerns the treatment of certain employer-owned life insurance contracts. No comments received on the 2023 proposed regulations expressed an opposing view on this point.</P>
                <P>Consistent with these comments supporting the 2023 proposed regulations under section 101 regarding the treatment of section 1035 exchanges, the final regulations retain those provisions with clarifying changes to address the treatment of boot in a section 1035 exchange. These include clarifying changes to the description of a “section 1035 exchange” in §§ 1.101-1(a)(1) and 1.6050Y-1(a)(1) of the 2023 proposed regulations. Additionally, clarifying changes are made to § 1.101-1(b)(2)(iv)(B) of the 2023 proposed regulations. As clarified, § 1.101-1(b)(2)(iv)(B) of the final regulations provides that, in certain circumstances, the amount of boot received tax-free in a section 1035 exchange will reduce the amount of proceeds attributable to the old interest that is excludable from gross income under section 101(a) and will therefore also reduce the amount of proceeds attributable to the new interest that is excludable from gross income under section 101(a). This clarification is consistent with the rules in § 1.101-1(b)(3) of the 2019 final regulations and section 1031(d).</P>
                <HD SOURCE="HD3">B. Request for Clarification Regarding State Insurable Interest Laws</HD>
                <P>Two of the commenters remarked on the requirement in section 7702(a) of the Code that a contract must be a “life insurance contract under the applicable law” to qualify as a life insurance contract for purposes of the Code. The commenters observed that a contract issued in a purported section 1035 exchange does not qualify as a life insurance contract for purposes of the Code if the contract violates applicable State insurance law, including State “insurable interest” laws, which the commenters described as generally requiring that a policyholder have a substantial family, business, or financial relationship with the insured individual other than the life insurance contract. The commenters noted that, in such a case, section 101 would not apply to exclude the death benefit under the contract from gross income.</P>
                <P>
                    One of the commenters expressed the view that it is not necessary to retain the 
                    <PRTPAGE P="42347"/>
                    significant expansion of the transfer for value rule that was reflected in the 2019 final regulations in order to discourage or prevent section 1035 exchanges if the exchange would violate State insurable interest laws because current and longstanding Federal income tax rules and potential adverse consequences under State law already provide an incentive to comply with such State laws. Consistent with this comment, the final regulations adopt, as proposed, the provisions of the 2023 proposed regulations reversing the expansion of the transfer for value rule with respect to section 1035 exchanges reflected in the 2019 final regulations.
                </P>
                <P>The other commenter noted that the 2023 proposed regulations may have the unintended effect of creating some confusion in the marketplace about whether the “applicable law” requirement of section 7702(a) continues to apply. The commenter suggested that the Treasury Department and the IRS clarify as part of the process of finalizing the 2023 proposed regulations that a contract issued as part of a purported section 1035 exchange remains subject to other requirements of the Code, such as the requirement in section 7702(a) that the contract issued in an exchange constitute a life insurance contract under the Code, which would require that it be treated as a life insurance contract under applicable State law.</P>
                <P>Regardless of whether a contract is issued in a section 1035 exchange, it must be described in section 7702(a) to be considered a life insurance contract under section 101. Section 7702(a) requires, among other things, that a contract be a “life insurance contract under the applicable law,” State or foreign law, as applicable. The 2023 proposed regulations under sections 101 and 6050Y address the consequences under sections 101 and 6050Y in cases in which a life insurance contract is issued in a section 1035 exchange. The 2023 proposed regulations do not affect the application of other Code sections, including, for instance, sections 1035 and 7702. The 2023 proposed regulations, consequently, do not affect the determination of whether a contract issued in a purported section 1035 exchange qualifies as a life insurance contract under section 7702(a) for purposes of the Code or whether an exchange of contracts qualifies as a section 1035 exchange. The same is true of the final regulations.</P>
                <P>A third commenter applauded the Treasury Department for proposing to modify the 2019 final regulations to allow employers to pursue section 1035 exchanges of contracts covering the lives of persons who are no longer actively employed. This comment could be read as suggesting that, with respect to section 1035 exchanges, the 2023 proposed regulations change the requirement under section 7702(a) that a contract be a “life insurance contract under the applicable law” to qualify as a life insurance contract for purposes of the Code. However, this is not the case. Neither the 2023 proposed regulations nor the final regulations change this requirement.</P>
                <HD SOURCE="HD3">C. Requests for Clarification Regarding Other Rules and Guidance</HD>
                <P>One commenter requested confirmation that the circumstances described in Notice 2009-48, 2009-24 I.R.B. 1085, Q&amp;As 14 and 15, do not give rise to a material change in employer-owned life insurance contracts for purposes of applying section 101(j). This commenter also requested clarification that a forgiveness of loaned policy cash value or distribution of cash or other property as a result of an exchange would be recognized as taxable gain under section 1031(b) of the Code, but an enhancement of policy cash value by the new carrier to offset a loss of the exchanged value from the old policy would not be treated as a taxable event. The requests for clarification regarding sections 101(j) and 1031 are not limited to situations involving life insurance contracts acquired in reportable policy sales and are beyond the scope of these regulations, which address the application of sections 101(a) and 6050Y to life insurance contracts acquired in reportable policy sales.</P>
                <P>This commenter also remarked that the 2023 proposed regulations do not address Rev. Rul. 2011-9, 2011-12 I.R.B. 554. This revenue ruling concerns the application to section 1035 exchanges of life insurance contracts of section 264(f)(1) of the Code, which disallows any deduction for the portion of a taxpayer's “interest expense” that is allocable to unborrowed policy cash values of life insurance contracts and annuity and endowment contracts. The commenter expressed the understanding that the 2023 proposed regulations render the employee exception in Rev. Rul. 2011-9 moot and requested that this point be clarified. However, the section 264 issue addressed in Rev. Rul. 2011-9 is also outside the scope of these final regulations under sections 101 and 6050Y. Neither the 2023 proposed regulations nor the final regulations affect Rev. Rul. 2011-9 or the conclusion set forth therein.</P>
                <HD SOURCE="HD3">D. Request for Changes to Information Reporting Obligations and Procedures</HD>
                <P>
                    As described in the preamble to the 2023 proposed regulations, to ensure proper reporting of reportable death benefits paid under contracts issued in section 1035 exchanges, § 1.6050Y-3(a) of the 2023 proposed regulations would require reporting by each “6050Y(b) issuer” that is a “section 1035 issuer” with respect to each “seller” at the time of the exchange. The 2023 proposed regulations would generally impose a reporting obligation on both the issuer of the old interest (old issuer) and the issuer of the new interest (new issuer) in a section 1035 exchange if the policyholder (seller) is exchanging an interest in a life insurance contract that has been transferred in an RPS. The preamble to the 2023 proposed regulations indicated that it is anticipated that this reporting will be completed on Form 1099-SB, 
                    <E T="03">Seller's Investment in Life Insurance Contract,</E>
                     and the information to be provided would include the policy number and identification of the transaction as a section 1035 exchange.
                </P>
                <P>One commenter agreed with the Treasury Department and the IRS that modifying the information reporting rules is the right way to address the concern that prompted the inclusion of the section 1035 exchange rules in the 2019 final regulations, which related to the possibility that a contract transferred in an RPS subsequently could be exchanged for a new contract pursuant to section 1035 and the death benefits under the new contract might not be reported under section 6050Y(c). The commenter recommended that the Treasury Department and the IRS finalize the information reporting requirements in a manner that takes into account public comments that may simplify or clarify such requirements or otherwise reduce the administrative burdens imposed on the taxpayers charged with implementing them. The commenter did not, however, make any specific burden reduction recommendations.</P>
                <P>
                    Another commenter suggested changes to the provisions of the 2023 proposed regulations related to tracking and information reporting requirements for section 1035 exchanges of RPS contracts. The commenter noted that the 2023 proposed regulations would (1) track the RPS status of a contract in an exchange by the policy owner, (2) assure the death benefits paid on such a contract are reported for tax purposes, and (3) be consistent with the remainder of the section 6050Y tax reporting regime. The commenter suggested that 
                    <PRTPAGE P="42348"/>
                    these goals could be achieved with less risk of confusion for policyholders and less administrative burden on insurers than under the 2023 proposed regulations. While expressing appreciation for the need to track the RPS tax attribute of a life insurance contract more formally, the commenter asserted that the requirement in § 1.6050Y-3(a) of the 2023 proposed regulations that the old issuer and new issuer file an information return with the IRS with respect to the section 1035 exchange is not necessary to accomplish the desired compliance goals and should therefore be removed. The commenter also suggested removing the requirement in § 1.6050Y-3(d)(1) of the 2023 proposed regulations that section 6050Y(b) issuers furnish a statement to sellers (policyholders) who make a section 1035 exchange. Additionally, the commenter expressed concerns regarding the anticipated use of Form 1099-SB for reporting section 1035 exchanges of RPS contracts.
                </P>
                <P>
                    The commenter noted that insurers involved in a section 1035 exchange typically share relevant information, including cost basis, without the use of an official IRS form. 
                    <E T="03">See, e.g.,</E>
                     § 35.3405-1(T), Q&amp;A (E-8), of the Employment Tax Regulations. The commenter stated that the existing process established for companies to share critical information about contracts exchanged is effective and that the RPS tax attribute could be incorporated in this reliable and established practice. The commenter suggested modifying § 1.6050Y-3 of the 2019 final regulations to require the issuer of the existing RPS contract to furnish a statement to the issuer of a new contract received in exchange for the RPS contract in a section 1035 exchange. Also, because the old issuer already must use Form 1099-R, 
                    <E T="03">Distributions From Pensions, Annuities, Retirement or Profit-Sharing Plans, IRAs, Insurance Contracts, etc.,</E>
                     to report section 1035 exchanges, the commenter recommended adding a new distribution code for Box 7 of Form 1099-R that would indicate that the section 1035 exchange being reported is an exchange of an RPS contract. Insurance companies currently report section 1035 exchanges of life insurance contracts on Form 1099-R with a distribution code “6” in Box 7, which identifies the distribution as a tax-free section 1035 exchange.
                </P>
                <P>After consideration of the comments received on the provisions of the 2023 proposed regulations relating to information reporting obligations and procedures, the Treasury Department and the IRS have determined that the filing of information returns with the IRS by the old issuer and new issuer with respect to section 1035 exchanges of RPS contracts is not necessary to accomplish the desired compliance goals. These goals can be addressed through the old issuer's Form 1099-R reporting of the section 1035 exchange and the related exchange of information between the old issuer and the new issuer.</P>
                <P>Accordingly, the following modifications to the proposed information reporting rules set forth in the 2023 proposed regulations are made in the final regulations: (1) the definition of “issuer” in § 1.6050Y-1(a)(8) of the 2019 final regulations is not expanded to include “section 1035 issuers”; (2) no change is made to §§ 1.6050Y-1(a)(14) and (18) and 1.6050Y-3(c) of the 2019 final regulations because the changes proposed in the 2023 proposed regulations are no longer necessary; (3) the requirement under § 1.6050Y-3(a) of the 2023 proposed regulations for section 1035 issuers (both old issuers described in § 1.6050Y-1(a)(8)(v)(A) of the 2023 proposed regulations and new issuers described in § 1.6050Y-1(a)(8)(v)(B) of the 2023 proposed regulations) to file information returns is not adopted; (4) the exception from reporting set forth in § 1.6050Y-4(e)(3) of the 2023 proposed regulations is modified and clarified; and (5) the reporting requirements under § 1.6050Y-3(a) and (d) of the 2023 proposed regulations for section 1035 issuers to furnish statements are not adopted and reporting with respect to section 1035 exchanges is instead required under new § 1.6050Y-3(h). Section 1.6050Y-3(h) of the final regulations applies to section 1035 exchanges that are treated as the transfer of an interest in a life insurance contract in a reportable policy sale under § 1.101-1(c)(3) of the final regulations, but only if the new issuer is not the old issuer. To ensure proper reporting when a reportable death benefit is paid under the new contract, the old issuer will provide certain information to the new issuer, including the policyholder's investment in the contract with respect to the old interest and a statement indicating whether the old issuer would have reported a payment of reportable death benefits under § 1.6050Y-4 of the final regulations had it paid death benefits attributable to the old interest on the date of the section 1035 exchange. The old issuer may use any reasonable method to provide this information to the new issuer.</P>
                <P>
                    Although issuers will have no obligation to furnish statements to policyholders making a section 1035 exchange under the final regulations, issuers may still have an obligation to furnish statements to policyholders with respect to a section 1035 exchange under other Code sections or regulations. 
                    <E T="03">See</E>
                     section 6047(d); Rev. Proc. 92-26, 1992-1 C.B. 744. The final regulations do not require additional reporting on the Form 1099-R, but it is anticipated that, as suggested by one of the commenters, a new distribution code for Box 7 of Form 1099-R will be added to indicate that the section 1035 exchange being reported is an exchange of an RPS contract. Such reporting will not be required before the IRS publishes both a final Form 1099-R reflecting such a requirement and final instructions for completing such form.
                </P>
                <HD SOURCE="HD2">2. Comments Relating to the De Minimis Exception for Ordinary Course Mergers and Acquisitions</HD>
                <P>
                    As described in the preambles to the 2019 final regulations and the 2023 proposed regulations, the 2019 final regulations include provisions that effectively exclude from the definition of RPS certain acquisitions of life insurance contracts, or interests therein, in ordinary course business transactions in which one trade or business acquires another trade or business that owns life insurance. Following the publication of the 2019 final regulations in the 
                    <E T="04">Federal Register</E>
                    , the Treasury Department and the IRS received a letter requesting the addition of an exception from the RPS rules for acquisitive transactions involving entities that own a de minimis amount of life insurance (for example, as a proportion of the total value of the transaction). More specifically, the author proposed that the Treasury Department and the IRS consider a further exception for transactions in which the amount of life insurance acquired as a result of an acquisitive transaction (and any related acquisitions) is five percent or less of the value of the acquired stock, assets, or both.
                </P>
                <P>
                    Section 1.101-1(c)(2)(v) of the 2023 proposed regulations provides an exception from the definition of “reportable policy sale” for direct acquisitions of interests in life insurance contracts from a C corporation by a C corporation if (1) the acquisition results from a transaction that qualifies as a reorganization under section 368(a); (2) immediately before the acquisition, (i) the interest is held by a C corporation that conducts an active trade or business within the meaning of § 1.367(a)-2(d)(2) and (3), (ii) the C corporation does not engage in a trade or business of investing in interests in life insurance contracts, and (iii) no more than 5 
                    <PRTPAGE P="42349"/>
                    percent of the gross value of the assets of the C corporation consists of life insurance contracts; and (3) immediately after the acquisition, (i) the acquiring C corporation does not engage in a trade or business of investing in interests in life insurance contracts, and (ii) not more than 5 percent of the gross value of the assets of the C corporation consists of life insurance contracts. The two comments received on the de minimis exception for ordinary course mergers and acquisitions set forth in § 1.101-1(c)(2)(v) of the 2023 proposed regulations agreed that the transactions covered by proposed § 1.101-1(c)(2)(v) should not be reportable policy sales but also requested certain expansions of the exception. Both commenters urged that the de minimis exception be expanded to cover certain taxable transactions, rather than just transactions that qualify as tax-free reorganizations under section 368(a) as provided by § 1.101-1(c)(2)(v)(D) of the 2023 proposed regulations.
                </P>
                <P>One commenter asserted that this limitation is unnecessary and potentially confusing because it could result in disparate treatment of taxpayers engaged in very similar ordinary course business acquisitions that are structured differently for non-tax business reasons with no clear policy reason for why these transactions should have different results under section 101. This commenter also recommended removing the requirement in § 1.101-1(c)(2)(v)(A) of the 2023 proposed regulations that the interest in a life insurance contract be held, immediately before acquisition, by a C corporation that conducts an active trade or business within the meaning of § 1.367(a)-2(d)(2) and (3) because it is unnecessarily restrictive. The commenter noted that acquisitive transactions often occur at the holding company level as opposed to the operating subsidiary level and a holding company may not technically meet the “active trade or business” standard even though the holding company owns operating subsidiaries that are engaged in active trades or businesses. The commenter made an alternative recommendation of modifying § 1.101-1(c)(2)(v)(A) of the 2023 proposed regulations to permit the interest to be held by a C corporation that is engaged in an active trade or business or is a member of an affiliated group that includes one or more members engaged in an active trade or business. The commenter asserted that this approach would be consistent with section 355(b)(3) and the regulations promulgated thereunder, upon which the section 367 regulations appear to have been originally based and which, pursuant to subsequent revisions that were made after the release of the relevant section 367 regulations, test the active conduct of a trade or business on an affiliated group level.</P>
                <P>The other commenter similarly urged that the de minimis exception should not be limited to transactions that qualify as a tax-free reorganization under section 368(a), and further, that it should also apply to acquisitive transactions of non-C corporation targets. This commenter highlighted the acknowledgement in the preamble to the 2023 proposed regulations that “C corporations are not frequently used as vehicles for investing in life insurance contracts covering insureds with respect to which the corporation does not have a substantial business, financial, or family relationship at the time the contract is issued because a corporate level income tax applies to corporate earnings in addition to income tax on distributions at the shareholder level” and asserted that other types of business entities also “are not frequently used as vehicles for investing in life insurance contracts covering insureds with respect to which the corporation does not have a substantial business, financial, or family relationship at the time the contract is issued.” This commenter also remarked that it is concerning that transactions with identical (or nearly identical) economic substance may have divergent outcomes with respect to whether the transaction gives rise to an RPS depending on the transaction's form. This commenter further asserted that there are a number of legal, economic, and business reasons why it is highly unlikely that ordinary course business acquisitions involving meager amounts of life insurance contracts can simply be restructured to meet the form-driven rules of either the 2023 proposed regulations or the 2019 final regulations, but that negative outcomes with respect to these incidentally transferred insurance contracts do have significant consequences to a variety of stakeholders. Finally, the commenter expressed concern that since the issuance of the 2019 final regulations, the life insurance industry has continued to see a number of circumstances where transactions that are wholly unrelated to the transfer of life insurance contracts have unclear outcomes under the RPS rules. For these reasons, the commenter urged that the de minimis exception be expanded to entities other than C corporations and regardless of the type of acquisitive transaction involved.</P>
                <P>After consideration of the comments received on the de minimis exception for ordinary course mergers and acquisitions set forth in § 1.101-1(c)(2)(v) of the 2023 proposed regulations, the final regulations adopt this provision without change. The Treasury Department and the IRS will continue to consider the possibility of proposing a rule broader than the one set forth in the 2023 proposed regulations, but will not delay the adoption of the 2023 proposed regulations supported by commenters while studying the issue. The Treasury Department and the IRS invite additional comments regarding the scope of the de minimis exception.</P>
                <HD SOURCE="HD2">3. Comments Relating to the Applicability Date</HD>
                <P>
                    In general, the 2023 proposed regulations would apply to certain transactions occurring on or after the date the 2023 proposed regulations are finalized. 
                    <E T="03">See</E>
                     §§ 1.101-6(c) and 1.6050Y-1(b)(2) of the 2023 proposed regulations. The commenter requesting changes to the information reporting provisions of the 2023 proposed regulations discussed in part 1.D of this Summary of Comments and Explanation of Revisions also requested transition relief from the reporting obligations if the proposed reporting changes suggested by the commenter were not adopted. Because the final regulations adopt the commenter's suggested reporting changes, no transition relief is provided in the final regulations. The applicability date provisions in the 2023 proposed regulations are adopted in the final regulations. 
                    <E T="03">See</E>
                     §§ 1.101-6(c) and 1.6050Y-1(b)(2) of the final regulations. However, for administrative reasons, § 1.6050Y-1(b) is republished in its entirety in the final regulations to reflect all changes to § 1.6050Y-1(b), including the ministerial changes set out in the 2023 proposed regulations to address the addition of § 1.6050Y-1(b)(2).
                </P>
                <HD SOURCE="HD1">Special Analyses</HD>
                <HD SOURCE="HD2">I. Regulatory Planning and Review—Economic Analysis</HD>
                <P>These final regulations are not subject to review under section 6(b) of Executive Order 12866 pursuant to the Memorandum of Agreement (July 4, 2025) between the Treasury Department and the Office of Management and Budget (OMB) regarding review of tax regulations.</P>
                <HD SOURCE="HD2">II. Paperwork Reduction Act</HD>
                <P>
                    The additional collection of information relating to the final regulations has been reviewed and 
                    <PRTPAGE P="42350"/>
                    approved by OMB in accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3507(d)) under OMB Control Number 1545-0119. In general, the additional collection of information is required for purposes of enforcing section 6050Y. When an interest in a life insurance contract that was previously transferred, or is treated as having been previously transferred, in an RPS (old contract) is exchanged by a policyholder under section 1035 for a new life insurance contract (new contract), § 1.6050Y-3(h) of the final regulations requires the issuer of the old contract (old issuer) to notify the issuer of the new contract (new issuer) of the status of the old contract as a contract transferred, or treated as having been transferred, in an RPS and to provide the investment in the contract for the old contract. This information is necessary to carry out the purpose of section 6050Y(c), which requires a payor of reportable death benefits to report certain information about payments of reportable death benefits.
                </P>
                <P>The additional collection of information in § 1.6050Y-3(h) of the final regulations was suggested by commenters on the proposed regulations as a simpler and less burdensome alternative to the collection of information rules in the proposed regulations, especially because most old issuers routinely provide new issuers with relevant information about the contract being exchanged, including relevant RPS information. Because the additional collection of information would achieve the goal of providing the information necessary for the proper reporting of reportable death benefits, the final regulations eliminate the reporting obligations that would have been imposed by § 1.6050Y-3 of the 2023 proposed regulations on new issuers with respect to section 1035 exchanges and reduce the reporting obligations that would have been imposed by § 1.6050Y-3 of the 2023 proposed regulations on old issuers with respect to section 1035 exchanges.</P>
                <P>The likely respondents to the collection of information are life insurance companies.</P>
                <P>
                    The burden for the additional collection of information contained in § 1.6050Y-3 of the final regulations will be reflected on Form 1099-R, 
                    <E T="03">Distributions From Pensions, Annuities, Retirement or Profit-Sharing Plans, IRAs, Insurance Contracts, etc.,</E>
                     when the burden is revised to reflect the additional collection of information in § 1.6050Y-3. The burden also will be revised when a new distribution code for Box 7 of Form 1099-R is added to indicate that the section 1035 exchange being reported is an exchange of an RPS contract. The OMB Control Number for Form 1099-R is 1545-0119. The final regulations eliminate the burden on policyholders making section 1035 exchanges of RPS contracts imposed by § 1.6050Y-2 of the 2019 final regulations. The burden on Form 1099-LS, 
                    <E T="03">Reportable Life Insurance Sale,</E>
                     will accordingly be reduced when the burden is revised. The OMB Control Number for Form 1099-LS is 1545-2281.
                </P>
                <HD SOURCE="HD2">III. Regulatory Flexibility Act</HD>
                <P>The Regulatory Flexibility Act (RFA) requires agencies to “prepare and make available for public comment an initial regulatory flexibility analysis,” which will “describe the impact of the proposed rule on small entities.” 5 U.S.C. 603(a). Section 605(b) of the RFA allows an agency to certify a rule, in lieu of preparing an analysis, if the proposed rulemaking is not expected to have a significant economic impact on a substantial number of small entities.</P>
                <P>Pursuant to the RFA, it is hereby certified that the final regulations will not have a significant economic impact on a substantial number of small entities, because any effect on small entities by the rules finalized in this document flows directly from section 13520 of Public Law 115-97, 131 Stat. 2054, 2148, 2151 (2017), commonly known as the Tax Cuts and Jobs Act (TCJA). In addition, it is anticipated that requirements in the final regulations, which implement the statutory requirements under section 13520 of the TCJA, will fall primarily on financial and insurance firms with annual receipts greater than $47 million and, therefore, on no small entities. Therefore, the Secretary of the Treasury hereby certifies that the final regulations will not have a significant economic impact on a substantial number of small entities.</P>
                <P>Pursuant to section 7805(f) of the Code, the notice of proposed rulemaking preceding the final regulations was submitted to the Chief Counsel for the Office of Advocacy of the Small Business Administration for comment on its impact on small business, and no comments were received.</P>
                <HD SOURCE="HD2">IV. Unfunded Mandates Reform Act</HD>
                <P>Section 202 of the Unfunded Mandates Reform Act of 1995 (UMRA) requires that agencies assess anticipated costs and benefits and take certain other actions before issuing a final rule that includes any Federal mandate that may result in expenditures in any one year by a State, local, or Tribal government, in the aggregate, or by the private sector, of $100 million in 1995 dollars, updated annually for inflation. This rule does not include any Federal mandate that may result in expenditures by State, local, or Tribal governments, or by the private sector in excess of that threshold.</P>
                <HD SOURCE="HD2">V. Executive Order 13132: Federalism</HD>
                <P>Executive Order 13132 (Federalism) prohibits an agency from publishing any rule that has federalism implications if the rule either imposes substantial, direct compliance costs on State and local governments, and is not required by statute, or preempts State law, unless the agency meets the consultation and funding requirements of section 6 of the Executive order. These final regulations do not have federalism implications and do not impose substantial direct compliance costs on State and local governments or preempt State law within the meaning of the Executive order.</P>
                <HD SOURCE="HD2">VI. Congressional Review Act</HD>
                <P>
                    Pursuant to the Congressional Review Act (5 U.S.C. 801 
                    <E T="03">et seq.</E>
                    ), the Office of Information and Regulatory Affairs has designated this rule as not a “major rule,” as defined by 5 U.S.C. 804(2).
                </P>
                <HD SOURCE="HD2">Drafting Information</HD>
                <P>The principal author of these regulations is Allan H. Sakaue, Office of Associate Chief Counsel (Financial Institutions and Products), IRS. However, other personnel from the Treasury Department and the IRS participated in their development.</P>
                <HD SOURCE="HD2">Statement of Availability of IRS Documents</HD>
                <P>
                    Any IRS Revenue Procedure, Revenue Ruling, Notice, or other guidance cited in this document is published in the Internal Revenue Bulletin (or Cumulative Bulletin) and is available from the Superintendent of Documents, U.S. Government Publishing Office, Washington, DC 20402, or by visiting the IRS website at 
                    <E T="03">https://www.irs.gov.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 26 CFR Part 1</HD>
                    <P>Income taxes, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Adoption of Amendments to the Regulations</HD>
                <P>Accordingly, the Treasury Department and IRS amend 26 CFR part 1 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1—INCOME TAXES</HD>
                </PART>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Paragraph 1.</E>
                         The authority citation for part 1 continues to read in part as follows:
                    </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>26 U.S.C. 7805 * * *</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <PRTPAGE P="42351"/>
                    <AMDPAR>
                        <E T="04">Par. 2.</E>
                         Section 1.101-1 is amended by:
                    </AMDPAR>
                    <AMDPAR>1. Adding a heading to paragraph (a) and a sentence after the fourth sentence of paragraph (a)(1);</AMDPAR>
                    <AMDPAR>2. Revising the headings to paragraph (b) introductory text and paragraph (b)(2);</AMDPAR>
                    <AMDPAR>3. Adding paragraph (b)(2)(iv);</AMDPAR>
                    <AMDPAR>4. Adding a sentence at the end of paragraph (c)(1);</AMDPAR>
                    <AMDPAR>5. Revising paragraph (c)(2)(v);</AMDPAR>
                    <AMDPAR>6. Adding paragraph (c)(3);</AMDPAR>
                    <AMDPAR>7. In the last sentence of paragraph (e)(2), removing the language “, other than the issuance of a policy in an exchange pursuant to section 1035”;</AMDPAR>
                    <AMDPAR>8. Adding two sentences after the fourth sentence of paragraph (g)(11); and</AMDPAR>
                    <AMDPAR>9. Adding paragraphs (g)(17) through (19).</AMDPAR>
                    <P>The additions and revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1.101-1 </SECTNO>
                        <SUBJECT>Exclusion from gross income of proceeds of life insurance contracts payable by reason of death.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Exclusion from gross income</E>
                            —(1) 
                            <E T="03">In general.</E>
                             * * * The extent to which this exclusion applies in cases in which life insurance policies have been gratuitously transferred or issued in an exchange to which section 1035(a) or section 1031 (to the extent it relates to section 1035(a)) applies (section 1035 exchange) is stated in paragraph (b)(2) of this section. * * *
                        </P>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Transfers and exchanges of life insurance policies.</E>
                             * * *
                        </P>
                        <STARS/>
                        <P>
                            (2) 
                            <E T="03">Other transfers and exchanges.</E>
                             * * *
                        </P>
                        <STARS/>
                        <P>
                            (iv) 
                            <E T="03">Section 1035 exchanges.</E>
                             When an interest in a life insurance contract (old interest) is exchanged in a section 1035 exchange for an interest in a newly issued life insurance contract (new interest), except as otherwise provided by this section with respect to any portion of the new interest that is transferred or exchanged subsequent to the section 1035 exchange, the amount of the proceeds attributable to the new interest that is excludable from gross income under section 101(a) is determined under either paragraph (b)(2)(iv)(A) or paragraph (b)(2)(iv)(B) of this section.
                        </P>
                        <P>(A) If, at the time of the exchange, the entire amount of the proceeds attributable to the old interest would have been excludable from gross income under section 101(a), the entire amount of the proceeds attributable to the new interest is excludable from gross income.</P>
                        <P>(B) If, at the time of the exchange, less than the entire amount of the proceeds attributable to the old interest would have been excludable from gross income under section 101(a), the amount of the proceeds attributable to the new interest that is excludable from gross income is limited to the sum of the amount of the proceeds attributable to the old interest that would have been excludable at the time of the exchange and the premiums and other amounts paid with respect to the new interest by the policyholder, reduced (but not below zero) by amounts received by the policyholder under the new life insurance contract that are not received as an annuity, to the extent excludable from gross income under section 72(e). For purposes of this paragraph (b)(2)(iv)(B), the amount of the proceeds attributable to the old interest that would have been excludable at the time of the exchange is decreased by the amount of any money and the fair market value of any other property received by the policyholder in the exchange and increased by the amount of gain to the policyholder that was recognized on such exchange.</P>
                        <STARS/>
                        <P>(c) * * *</P>
                        <P>(1) * * * See paragraph (c)(3) of this section for special rules applicable to section 1035 exchanges.</P>
                        <P>(2) * * *</P>
                        <STARS/>
                        <P>(v) The direct acquisition of an interest in a life insurance contract by a C corporation if:</P>
                        <P>(A) Immediately before the acquisition, the interest is held by another C corporation (target C corporation) that actively conducts a trade or business within the meaning of § 1.367(a)-2(d)(2) and (3);</P>
                        <P>(B) Immediately before the acquisition, the target C corporation does not engage in a trade or business of investing in interests in life insurance contracts;</P>
                        <P>(C) Immediately before the acquisition, no more than 5 percent of the gross value of the assets (as determined under paragraph (f)(4) of this section) of the target C corporation consists of life insurance contracts;</P>
                        <P>(D) The acquisition results from a transaction that qualifies as a reorganization under section 368(a) with respect to which the target C corporation and the acquiring C corporation each is a party to the reorganization (within the meaning of section 368(b));</P>
                        <P>(E) Immediately after the acquisition, the acquiring C corporation does not engage in a trade or business of investing in interests in life insurance contracts; and</P>
                        <P>(F) Immediately after the acquisition, no more than 5 percent of the gross value of the assets (as determined under paragraph (f)(4) of this section) of the acquiring C corporation consists of life insurance contracts.</P>
                        <P>
                            (3) 
                            <E T="03">Section 1035 exchanges.</E>
                             This paragraph (c)(3) applies if an interest in a life insurance contract (old interest) is exchanged in a section 1035 exchange for an interest in a newly issued life insurance contract (new interest), and the old interest previously was transferred for valuable consideration in a reportable policy sale under paragraph (c)(1) of this section or is treated as an interest in a life insurance contract that previously was transferred for valuable consideration in a reportable policy sale under this paragraph (c)(3). For purposes of this section, the new interest is treated as an interest in a life insurance contract that previously was transferred for valuable consideration in a reportable policy sale. For purposes of §§ 1.6050Y-3(h) and 1.6050Y-4, the section 1035 exchange is treated as the transfer of an interest in the life insurance contract in a reportable policy sale.
                        </P>
                        <STARS/>
                        <P>(g) * * *</P>
                        <P>(11) * * * Also, the exception in paragraph (c)(2)(v) of this section applies, provided Corporation X satisfies the requirements of paragraphs (c)(2)(v)(A) through (C) of this section immediately before the acquisition by Corporation Y, and Corporation Y satisfies the requirements of paragraphs (c)(2)(v)(E) and (F) of this section immediately after the acquisition. This would be the case even if A were no longer employed by Corporation X at the time of the transfer. * * *</P>
                        <STARS/>
                        <P>
                            (17) 
                            <E T="03">Example 17.</E>
                             The facts are the same as in paragraph (g)(4) of this section (
                            <E T="03">Example 4</E>
                            ), except that, before A's death, C exchanges the policy on A's life for a new policy on A's life in a section 1035 exchange. The amount of the proceeds C may exclude from C's gross income under this section is limited under paragraph (b)(2)(iv)(B) of this section to $6,000 plus any premiums and other amounts paid by C with respect to the original policy subsequent to the transfer and any premiums and other amounts paid by C with respect to the new policy.
                        </P>
                        <P>
                            (18) 
                            <E T="03">Example 18.</E>
                             The facts are the same as in paragraph (g)(17) of this section (
                            <E T="03">Example 17</E>
                            ), except that, before A's death, C sells the new policy to A for fair market value. A's estate receives 
                            <PRTPAGE P="42352"/>
                            the proceeds of $100,000 on A's death. Under paragraph (b)(1)(ii)(B)(
                            <E T="03">3</E>
                            )(
                            <E T="03">i</E>
                            ) of this section, the amount of the proceeds A's estate may exclude from gross income is not limited by paragraph (b) of this section.
                        </P>
                        <P>
                            (19) 
                            <E T="03">Example 19.</E>
                             A is the initial policyholder of a $100,000 insurance policy on A's life. A transfers the policy for $6,000, its fair market value, to an individual, C, who does not have a substantial family, business, or financial relationship with A at the time of the transfer. The transfer from A to C is a reportable policy sale. C also is the initial policyholder of a $200,000 insurance policy on A's life. Before A's death, C exchanges the two policies on A's life for a single new policy on A's life in a section 1035 exchange. C receives the proceeds from the new policy on A's death. The entire amount of the proceeds attributable to the interest in the new policy that was issued in exchange for the policy originally issued to C is excludable from gross income under paragraph (b)(2)(iv)(A) of this section. The amount of the proceeds attributable to the interest in the new policy that was issued in exchange for the policy originally issued to A that is excludable from gross income is limited under paragraph (b)(2)(iv)(B) of this section to $6,000 plus any premiums and other amounts paid by C with respect to the policy originally issued to A subsequent to the transfer and any premiums and other amounts paid by C with respect to the interest in the new policy that was issued in exchange for the policy originally issued to A.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 3.</E>
                         Section 1.101-6 is amended by revising the section heading and adding paragraph (c) to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.101-6 </SECTNO>
                        <SUBJECT>Applicability date.</SUBJECT>
                        <STARS/>
                        <P>(c) Notwithstanding paragraphs (a) and (b) of this section, § 1.101-1(b)(2)(iv) and (c)(3) apply to any interest in a life insurance contract issued in a section 1035 exchange occurring on or after July 9, 2026, and § 1.101-1(c)(2)(v) applies to any acquisition of an interest in a life insurance contract occurring on or after July 9, 2026. Taxpayers may also choose to apply the rules in § 1.101-1(b)(2)(iv), (c)(2)(v), and (c)(3) to all exchanges and acquisitions occurring after December 31, 2017.</P>
                    </SECTION>
                </REGTEXT>
                <AMDPAR>
                    <E T="04">Par. 4.</E>
                     Section 1.6050Y-1 is amended by:
                </AMDPAR>
                <AMDPAR>1. Adding a sentence at the end of paragraph (a)(1);</AMDPAR>
                <AMDPAR>2. Revising and republishing paragraph (a)(2);</AMDPAR>
                <AMDPAR>3. Removing the last sentence in paragraph (a)(8)(ii);</AMDPAR>
                <AMDPAR>4. Adding the language “under § 1.101-1(c)(1) or (3)” at the end of paragraph (a)(12); and</AMDPAR>
                <AMDPAR>5. Revising and republishing paragraph (b).</AMDPAR>
                <P>The additions and revisions read as follows:</P>
                <SECTION>
                    <SECTNO>§ 1.6050Y-1</SECTNO>
                    <SUBJECT> Information reporting for reportable policy sales, transfers of life insurance contracts to foreign persons, and reportable death benefits.</SUBJECT>
                    <P>(a) * * *</P>
                    <P>
                        (1) * * * For purposes of determining the buyer under paragraph (a)(2) of this section, the term 
                        <E T="03">acquirer</E>
                         also includes any person to whom an interest in a life insurance contract (new interest) is issued in an exchange to which section 1035(a) or section 1031 (to the extent it relates to section 1035(a)) applies (section 1035 exchange) that is treated as the transfer of an interest in the life insurance contract in a reportable policy sale under § 1.101-1(c)(3).
                    </P>
                    <P>
                        (2) 
                        <E T="03">Buyer.</E>
                         The term 
                        <E T="03">buyer</E>
                         means, with respect to any interest in a life insurance contract that has been transferred in a reportable policy sale under § 1.101-1(c)(1) or treated as such an interest under § 1.101-1(c)(3), the person that was the most recent acquirer of that interest in a reportable policy sale as of the date reportable death benefits are paid under the contract.
                    </P>
                    <STARS/>
                    <P>
                        (b) 
                        <E T="03">Applicability dates</E>
                        —(1) 
                        <E T="03">In general.</E>
                         Except as otherwise provided in paragraph (b)(2) of this section, this section and §§ 1.6050Y-2 through 1.6050Y-3 apply to reportable policy sales made after December 31, 2018. Except as otherwise provided in paragraph (b)(2) of this section, this section and § 1.6050Y-4 apply to reportable death benefits paid after December 31, 2018. This section and § 1.6050Y-3 apply to any notice of a transfer to a foreign person received after December 31, 2018. However, for reportable policy sales and payments of reportable death benefits occurring after December 31, 2018, and on or before December 31, 2019, and any notice of a transfer to a foreign person received after December 31, 2018, and on or before December 31, 2019, transition relief is provided as follows:
                    </P>
                    <P>(i) Statements required to be furnished to issuers under section 6050Y(a)(2) and § 1.6050Y-2(d)(2)(i) must be furnished by the later of the applicable deadline set forth in § 1.6050Y-2(d)(2)(ii) or December 30, 2019.</P>
                    <P>(ii) Statements required to be furnished to reportable policy sale payment recipients under section 6050Y(a)(2) and § 1.6050Y-2(d)(1)(i) must be furnished by the later of the applicable deadline set forth in § 1.6050Y-2(d)(1)(ii) or February 28, 2020.</P>
                    <P>(iii) Statements required to be furnished to sellers under section 6050Y(b)(2) and § 1.6050Y-3(d)(1) must be furnished by the later of the applicable deadline set forth in § 1.6050Y-3(d)(2) or February 28, 2020.</P>
                    <P>(iv) Statements required to be furnished to reportable death benefits payment recipients under section 6050Y(c)(2) and § 1.6050Y-4(c)(1) must be furnished by the later of the applicable deadline set forth in § 1.6050Y-4(c)(2) or February 28, 2020.</P>
                    <P>(v) Returns required to be filed under section 6050Y(a)(1) and § 1.6050Y-2(a), section 6050Y(b)(1) and § 1.6050Y-3(a), and section 6050Y(c)(1) and § 1.6050Y-4 must be filed by the later of the applicable deadline set forth in § 1.6050Y-2(c), § 1.6050Y-3(c), and § 1.6050Y-4(b) or February 28, 2020.</P>
                    <P>
                        (2) 
                        <E T="03">Section 1035 exchanges.</E>
                         Sections 1.6050Y-1, 1.6050Y-2, and 1.6050Y-3 apply to any life insurance contract acquired in a section 1035 exchange that occurs on or after July 9, 2026. Section 1.6050Y-4 applies to reportable death benefits paid with respect to an interest in a life insurance contract issued in a section 1035 exchange if the exchange occurs on or after July 9, 2026.
                    </P>
                </SECTION>
                <SECTION>
                    <SECTNO>§ 1.6050Y-2 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 5.</E>
                         Section 1.6050Y-2 is amended by removing paragraph (f)(3).
                    </AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 6.</E>
                         Section 1.6050Y-3 is amended by:
                    </AMDPAR>
                    <AMDPAR>1. In paragraph (f) introductory text, removing the language “paragraph (f)(1), (2), or (3) of this section applies” at the end of the paragraph and adding in its place “paragraph (f)(1) or (2) of this section applies”;</AMDPAR>
                    <AMDPAR>2. Removing paragraph (f)(3); and</AMDPAR>
                    <AMDPAR>3. Adding paragraph (h).</AMDPAR>
                    <P>The addition reads as follows:</P>
                    <SECTION>
                        <SECTNO>§ 1.6050Y-3</SECTNO>
                        <SUBJECT> Information reporting by 6050Y(b) issuers for reportable policy sales and transfers of life insurance contracts to foreign persons.</SUBJECT>
                        <STARS/>
                        <P>
                            (h) 
                            <E T="03">Information to be provided by old issuer to new issuer for certain section 1035 exchanges</E>
                            —(1) 
                            <E T="03">Scope.</E>
                             This paragraph (h)(1) applies to a section 1035 exchange in which an interest in a life insurance contract (old interest) is exchanged by a policyholder for an interest in a newly issued life insurance contract (new interest), and the old interest previously was transferred for valuable consideration in a reportable 
                            <PRTPAGE P="42353"/>
                            policy sale under § 1.101-1(c)(1) or is treated as an interest in a life insurance contract that previously was transferred for valuable consideration in a reportable policy sale under § 1.101-1(c)(3). However, this paragraph (h)(1) does not apply if the issuer of the old interest (old issuer) and the issuer of the new interest (new issuer) are the same.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Provision of information.</E>
                             If paragraph (h)(1) of this section applies to a section 1035 exchange, the old issuer will provide to the new issuer the information necessary to ensure proper reporting of reportable death benefits under § 1.6050Y-4. This information includes the policyholder's investment in the contract with respect to the old interest and a statement indicating whether the old issuer would have reported a payment of reportable death benefits under § 1.6050Y-4 had it paid death benefits attributable to the old interest on the date of the section 1035 exchange. For example, if the old issuer had received, or had knowledge of another issuer having received, a statement described in § 1.6050Y-2(d)(2), the old issuer would include a statement that it would have reported a payment of reportable death benefits. Similarly, if the old issuer had other information indicating that the old interest previously was transferred for valuable consideration in a reportable policy sale under § 1.101-1(c)(1) or was treated as having been so transferred under § 1.101-1(c)(3), the old issuer would include a statement that it would have reported a payment of reportable death benefits.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Reasonable method.</E>
                             For purposes of paragraph (h)(2) of this section, the old issuer may use any reasonable method to provide the information described in paragraph (h)(2) of this section to the new issuer.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <AMDPAR>
                        <E T="04">Par. 7.</E>
                         Section 1.6050Y-4 is amended by adding a sentence at the end of paragraph (e)(3) to read as follows:
                    </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1.6050Y-4</SECTNO>
                        <SUBJECT> Information reporting by payors for reportable death benefits.</SUBJECT>
                        <STARS/>
                        <P>(e) * * *</P>
                        <P>(3) * * * Additionally, if the reportable death benefits are paid with respect to an interest in a life insurance contract issued in a section 1035 exchange, the payor never received, and has no knowledge of any issuer having received, information indicating that the interest was issued in exchange for an interest in a life insurance contract that previously was transferred for valuable consideration in a reportable policy sale or was treated as so transferred under § 1.101-1(c)(3).</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>Frank J. Bisignano,</NAME>
                    <TITLE>Chief Executive Officer.</TITLE>
                    <DATED>Approved: June 11, 2026.</DATED>
                    <NAME>Kevin M. Salinger,</NAME>
                    <TITLE>Deputy Assistant Secretary of the Treasury (Tax Policy).</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13830 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4831-GV-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <CFR>26 CFR Part 1</CFR>
                <DEPDOC>[TD 10051]</DEPDOC>
                <RIN>RIN 1545-BQ58</RIN>
                <SUBJECT>Charitable Remainder Annuity Trust Listed Transaction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document contains final regulations that identify certain charitable remainder annuity trust (CRAT) transactions and substantially similar transactions as listed transactions, a type of reportable transaction. Material advisors and certain participants in these listed transactions are required to file disclosures with the IRS and will be subject to penalties for failure to disclose. The final regulations affect participants in these transactions as well as material advisors but provide that certain organizations whose only role or interest in the transaction is as a charitable remainderman will not be treated as participants in the transaction or as parties to a prohibited tax shelter transaction subject to excise taxes and disclosure requirements.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>
                        <E T="03">Effective date:</E>
                         These regulations are effective on July 9, 2026.
                    </P>
                    <P>
                        <E T="03">Applicability date:</E>
                         For applicability date, 
                        <E T="03">see</E>
                         § 1.6011-15(e).
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Concerning the final regulations, Charles D. Wien of the Office of Associate Chief Counsel (Passthroughs, Trusts &amp; Estates) (202) 317-5279 (not a toll-free number).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Authority</HD>
                <P>This document amends the Income Tax Regulations (26 CFR part 1) by adding final regulations under section 6011 of the Internal Revenue Code (Code) to identify certain CRAT transactions as listed transactions, a type of reportable transaction (final regulations).</P>
                <P>Section 6001 of the Code provides an express delegation of authority to the Secretary of the Treasury or his delegate (Secretary) to require, either by notice served or by regulations, every taxpayer to keep the records, render the statements, make the returns, and comply with the rules and regulations that the Secretary deems necessary to demonstrate tax liability.</P>
                <P>Section 6011(a) of the Code provides an express delegation of authority to the Secretary to require every taxpayer to “make a return or statement according to the forms and regulations prescribed by the Secretary” and “include therein the information required by such forms or regulations.”</P>
                <P>Section 6707A(c) of the Code confirms the Secretary's authority to identify transactions as “reportable transactions” and as “listed transactions” and to require reporting of information relating to such transactions pursuant to the authority conferred by section 6011. Section 6707A(c)(1) defines the term “reportable transaction” to mean “any transaction with respect to which information is required to be included with a return or statement because, as determined under regulations prescribed under section 6011, such transaction is of a type which the Secretary determines as having a potential for tax avoidance or evasion.” In addition, section 6707A(c)(2) defines the term “listed transaction” to mean a reportable transaction that is “the same as, or substantially similar to, a transaction specifically identified by the Secretary as a tax avoidance transaction for purposes of section 6011.”</P>
                <P>The final regulations also are issued under the express delegation of authority under section 7805(a) of the Code, which authorizes the Secretary to “prescribe all needful rules and regulations for the enforcement of [the Code], including all rules and regulations as may be necessary by reason of any alteration of law in relation to internal revenue.”</P>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On March 25, 2024, the Department of Treasury (Treasury Department) and the IRS published a notice of proposed rulemaking (REG-108761-22) in the 
                    <E T="04">Federal Register</E>
                     (89 FR 20569) proposing regulations at new § 1.6011-15 (proposed § 1.6011-15) that would identify certain CRAT transactions and substantially similar transactions as “listed transactions” for purposes of 
                    <PRTPAGE P="42354"/>
                    § 1.6011-4 and sections 6111 and 6112 of the Code (proposed regulations). The Treasury Department and the IRS received one comment in response to the proposed regulations that are the subject of this final rulemaking. The comment is available for public inspection at 
                    <E T="03">https://www.regulations.gov</E>
                     or upon request. No public hearing was held on the proposed regulations because there were no requests to speak.
                </P>
                <HD SOURCE="HD1">Summary of and Response to Comment</HD>
                <P>The one comment received supports the proposed regulations and agrees that the transactions described in the proposed regulations miscomprehend the operation of the tier structure under section 664 that governs the characterization and taxation of distributions from CRATs. In addition, the commenter noted that the CRATs described in the proposed regulations have other technical flaws that would prevent the purported CRATs from qualifying as CRATs under section 664(d)(1).</P>
                <P>The commenter also agreed with the proposal that an organization described in section 170(c) of the Code that the purported CRAT designates as a recipient of the remainder interest is not treated as (1) a participant under § 1.6011-4(c)(3)(i)(A) in the transaction, or (2) as a party to the transaction for purposes of section 4965 of the Code solely by reason of its status as a recipient of the remainder interest described in section 664(d)(1). Further, the commenter pointed out that the charitable remainder beneficiary often is not even aware of the existence of its remainder interest until the charitable organization receives a distribution from the trust.</P>
                <P>The proposed regulations requested comments concerning whether a charitable remainder beneficiary could be a material advisor under section 6111(b)(1)(A), and asked, in particular, whether the charitable remainder beneficiary ever provides material aid, assistance, or advice with respect to transactions described in proposed § 1.6011-15(b), the nature of the services being provided, and what fees the charitable remainder beneficiary would receive for providing such material aid, assistance, or advice. In response to this request for comments, the commenter stated that, based on its experience, charitable remainder beneficiaries rarely provide material aid, assistance, or advice, and that any material aid, assistance, or advice is most often provided by the promoters of the transaction. Additionally, the commenter stated it is not aware of cases in which charitable remainder beneficiaries have received fees, either directly or indirectly, for providing material aid, assistance, or advice.</P>
                <P>However, the commenter noted that it is possible that a charity would provide general information about a CRAT to a participant in the listed transaction. Specifically, it would not be unusual for a charity to suggest consideration of a CRAT to a potential charitable donor or to explain to that potential donor the elements and operation of a trust that qualifies as a CRAT. The commenter requested that the final regulations make clear that a charitable remainder beneficiary will not be considered to provide material aid, assistance, or advice unless the charitable remainder beneficiary provides information that specifically endorses the abusive interpretation of the applicability and operation of the tier structure under which CRAT distributions are taxed by section 664(b).</P>
                <P>Section 301.6111-3(b)(1) provides that a person is a material advisor with respect to a transaction if the person provides any material aid, assistance, or advice with respect to organizing, managing, promoting, selling, implementing, insuring, or carrying out any reportable transaction and directly or indirectly derives gross income in excess of the threshold amount provided in § 301.6111-3(b)(3). Section 301.6111-3(b)(2)(i) provides that a person provides material aid, assistance, or advice if the person makes or provides a tax statement to or for the benefit of any person described in § 301.6111-3(b)(2)(i). Section 301.6111-3(b)(2)(ii) generally provides that a tax statement is any statement (including another person's statement), oral or written, that relates to a tax aspect of a transaction that causes the transaction to be a reportable transaction.</P>
                <P>A description of the effect of section 664(b) that includes, or a statement endorsing, the abusive interpretation of the application or operation of the tier structure under section 664(b) would be considered a tax statement as defined in § 301.6111-3(b)(2)(ii) as noted by the commenter, as would other statements regarding other elements of the transaction described in these final regulations, such as the validity of the terms of a CRAT used in the structure. However, a mere suggestion or description of a trust qualifying as a CRAT would not be a statement relating to a tax aspect of the transaction that causes the transaction to be a reportable transaction. As a result, as was discussed by the commenter, simply suggesting a donor's consideration of the creation of, or providing general information regarding, a trust qualifying as a CRAT would not be a tax statement that would result in the charity being a material advisor. Furthermore, to be a material advisor, the charitable remainderman must receive gross income (such as a fee) at least equal to the thresholds in § 301.6111-3(b)(3), and the commenter noted that it was not aware of charitable remaindermen receiving fees for providing material aid, assistance, or advice.</P>
                <P>Because the application of rules governing who is considered a material adviser seem sufficiently clear in this context, the Treasury Department and IRS have determined that it is unnecessary to address the issue in the regulatory text. Thus, the Treasury Department and IRS decline to adopt the proposed change recommended by the commenter in finalizing the proposed regulations, and the proposed regulations are adopted as final without change.</P>
                <HD SOURCE="HD1">Special Analyses</HD>
                <HD SOURCE="HD2">I. Regulatory Planning and Review</HD>
                <P>These regulations are not subject to review under section 6(b) of Executive Order 12866 pursuant to the Memorandum of Agreement (July 4, 2025) between the Treasury Department and the Office of Management and Budget (OMB) regarding review of tax regulations. Therefore, a regulatory impact assessment is not required.</P>
                <HD SOURCE="HD2">II. Paperwork Reduction Act</HD>
                <P>The estimated number of taxpayers impacted by these final regulations is between 50 to 100 per year. No burden on these taxpayers is imposed by these final regulations. Instead, the collection of information contained in these final regulations is reflected in the collection of information for Form 8886, Reportable Transaction Disclosure Statement, and Form 8918, Material Advisor Disclosure Statement, that have been reviewed and approved by the OMB in accordance with the Paperwork Reduction Act (44 U.S.C. 3507(c)) under control numbers 1545-1800 and 1545-0865.</P>
                <P>To the extent there is a change in burden as a result of these regulations, the change in burden will be reflected in the updated burden estimates for Forms 8886 and 8918. The requirement to maintain records to substantiate information on Forms 8886 and 8918 already is contained in the burden associated with the control numbers for the forms and remains unchanged.</P>
                <P>
                    An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information 
                    <PRTPAGE P="42355"/>
                    unless the collection of information displays a valid OMB control number.
                </P>
                <HD SOURCE="HD2">III. Regulatory Flexibility Act</HD>
                <P>
                    The Regulatory Flexibility Act (5 U.S.C. chapter 6) (RFA) requires the agency to “prepare and make available for public comment an initial regulatory flexibility analysis” which will “describe the impact of the proposed rule on small entities.” 5 U.S.C. 603(a). The term “small entities” is defined in 5 U.S.C. 601(6) to mean “small business,” “small organization,” and “small governmental jurisdiction,” which also are defined in 5 U.S.C. 601(3) through (5). Small business size standards define whether a business is “small” and have been established for types of economic activities, or industry, generally under the North American Industry Classification System (NAICS). 
                    <E T="03">See</E>
                     title 13, part 121 of the Code of Federal Regulations (titled “Small Business Size Regulations”). The size standards look at various factors, including annual receipts, number of employees, and amount of assets, to determine whether the business is small. 
                    <E T="03">See</E>
                     title 13, part 121.201 of the Code of Federal Regulations for the Small Business Size Standards by NAICS Industry.
                </P>
                <P>Section 605 of the Act allows an agency to certify a rule if the rulemaking is not expected to have a significant economic impact on a substantial number of small entities. The Treasury Department and the IRS hereby certify that these final regulations will not have a significant economic impact on a substantial number of small entities. This certification is based on the fact that the majority of the effect of the final regulations falls on individuals and trusts. Further, the Treasury Department and the IRS expect that the reporting burden is low; the information sought is necessary for regular annual return preparation and ordinary recordkeeping.</P>
                <P>For the reasons stated, a regulatory flexibility analysis under the RFA is not required. Pursuant to section 7805(f) of the Code, the proposed rule preceding this rulemaking was submitted to the Chief Counsel for the Office of Advocacy of the Small Business Administration for comment on its impact on small business and no comments were received.</P>
                <HD SOURCE="HD2">IV. Unfunded Mandates Reform Act</HD>
                <P>Section 202 of the Unfunded Mandates Reform Act of 1995 (UMRA) requires that agencies assess anticipated costs and benefits and take certain other actions before issuing a final rule that includes any Federal mandate that may result in expenditures in any one year by a State, local, or Tribal government, in the aggregate, or by the private sector, of $100 million (updated annually for inflation). This final rule does not include any Federal mandate that may result in expenditures by State, local, or Tribal governments, or by the private sector in excess of that threshold.</P>
                <HD SOURCE="HD2">V. Executive Order 13132: Federalism</HD>
                <P>Executive Order 13132 (Federalism) prohibits an agency from publishing any rule that has federalism implications if the rule either imposes substantial, direct compliance costs on State and local governments, and is not required by statute, or preempts State law, unless the agency meets the consultation and funding requirements of section 6 of the Executive order. This final rule does not have federalism implications and does not impose substantial direct compliance costs on State and local governments or preempt State law within the meaning of the Executive order.</P>
                <HD SOURCE="HD1">Drafting Information</HD>
                <P>The principal author of these final regulations is Charles D. Wien, Office of Associate Chief Counsel (Passthroughs, Trusts, &amp; Estates). However, other personnel from the IRS and the Treasury Department participated in the development of these regulations.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 26 CFR Part 1</HD>
                    <P>Income taxes, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Adoption of Amendments to the Regulations</HD>
                <P>Accordingly, the Treasury Department and the IRS amend 26 CFR part 1 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1—INCOME TAXES</HD>
                </PART>
                <REGTEXT TITLE="26" PART="1">
                    <P>
                        <E T="04">Paragraph 1.</E>
                         The authority citation for part 1 is amended by adding an entry for § 1.6011-15 in numerical order to read, in part, as follows:
                    </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 26 U.S.C. 7805 * * *</P>
                    </AUTH>
                    <EXTRACT>
                        <STARS/>
                        <P>Section 1.6011-15 also issued under 26 U.S.C. 6001 and 26 U.S.C. 6011.</P>
                        <STARS/>
                    </EXTRACT>
                </REGTEXT>
                <REGTEXT TITLE="26" PART="1">
                    <P>
                        <E T="04">Par. 2.</E>
                         Section 1.6011-15 is added to read as follows:
                    </P>
                    <SECTION>
                        <SECTNO>§ 1.6011-15 </SECTNO>
                        <SUBJECT>Charitable remainder annuity trust listed transaction.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">In general.</E>
                             Transactions that are the same as, or substantially similar to, a transaction described in paragraph (b) of this section are identified as listed transactions for purposes of § 1.6011-4(b)(2).
                        </P>
                        <P>
                            (b) 
                            <E T="03">Charitable remainder annuity trusts.</E>
                             A transaction is described in this paragraph (b) if:
                        </P>
                        <P>(1) The grantor creates a trust purporting to qualify as a charitable remainder annuity trust under section 664(d)(1) of the Internal Revenue Code (Code);</P>
                        <P>(2) The grantor funds the trust with property having a fair market value in excess of its basis (contributed property);</P>
                        <P>(3) The trustee sells the contributed property;</P>
                        <P>(4) The trustee uses some or all of the proceeds from the sale of the contributed property to purchase an annuity; and</P>
                        <P>(5) On a Federal income tax return, the beneficiary of the trust treats the annuity amount payable from the trust as if it were, in whole or in part, an annuity payment subject to section 72 of the Code, instead of as carrying out to the beneficiary amounts in the ordinary income and capital gain tiers of the trust in accordance with section 664(b).</P>
                        <P>
                            (c) 
                            <E T="03">Participation</E>
                            —(1) 
                            <E T="03">In general.</E>
                             A taxpayer has participated in a transaction identified as a listed transaction in paragraph (a) of this section if the taxpayer's tax return reflects tax consequences or a tax strategy described in this section as provided under § 1.6011-4(c)(3)(i)(A). These tax consequences include those tax consequences that would affect any gift tax return, whether or not such gift tax return was filed. 
                            <E T="03">See</E>
                             § 25.6011-4 of this chapter.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Treatment of charitable remainderman.</E>
                             An organization described in section 170(c) of the Code that the purported charitable remainder annuity trust designates as a recipient of the remainder interest described in section 664(d)(1) is not treated as a participant under § 1.6011-4(c)(3)(i)(A) in the transaction described in this section solely by reason of its status as a recipient of the remainder interest described in section 664(d)(1).
                        </P>
                        <P>
                            (d) 
                            <E T="03">Treatment of charitable remainderman under section 4965.</E>
                             A tax-exempt entity (as defined in section 4965 of the Code) that is an organization described in section 170(c) and that the purported charitable remainder annuity trust designates as a recipient of the remainder interest described in section 664(d)(1) is not treated as a party to the transaction described in this section for purposes of section 4965 solely by reason of its status as a recipient of the remainder interest described in section 664(d)(1).
                        </P>
                        <P>
                            (e) 
                            <E T="03">Applicability date.</E>
                             This section's identification of transactions that are the same as, or substantially similar to, the 
                            <PRTPAGE P="42356"/>
                            transaction described in paragraph (b) of this section as listed transactions for purposes of § 1.6011-4(b)(2) is effective on July 9, 2026.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <NAME>Frank J. Bisignano,</NAME>
                    <TITLE>Chief Executive Officer.</TITLE>
                    <DATED>Approved: April 15, 2026.</DATED>
                    <NAME>Kenneth J. Kies.</NAME>
                    <TITLE>Assistant Secretary of the Treasury (Tax Policy).</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13851 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4831-GV-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Parts 52 and 81</CFR>
                <DEPDOC>[EPA-R05-OAR-2023-0635; FRL-13222-02-R5]</DEPDOC>
                <SUBJECT>
                    Air Plan Approval; Michigan; Redesignation and Maintenance Plan for the Partial St. Clair 2010 1-Hour Sulfur Dioxide (SO
                    <E T="0735">2</E>
                    ) NAAQS Nonattainment Area
                </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Environmental Protection Agency (EPA) is taking final action to redesignate the St. Clair nonattainment area in southeast Michigan to attainment for the 2010 sulfur dioxide (SO
                        <E T="52">2</E>
                        ) National Ambient Air Quality Standard (NAAQS). The EPA is also approving Michigan's maintenance plan for the St. Clair SO
                        <E T="52">2</E>
                         nonattainment area and emissions limits for the DTE Belle River Power Plant. Michigan submitted the request for approval of the St. Clair area redesignation and maintenance plan on December 14, 2023, with a supplement to the request on July 24, 2025. The EPA proposed to approve this action on April 10, 2026, and received no adverse comments.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final rule is effective on July 9, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The EPA has established a docket for this action under Docket ID No. EPA-R05-OAR-2023-0635. All documents in the docket are listed on the 
                        <E T="03">https://www.regulations.gov</E>
                         website. Although listed in the index, some information is not publicly available, 
                        <E T="03">i.e.,</E>
                         Confidential Business Information (CBI), Proprietary Business Information (PBI), or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the internet and will be publicly available only in hard copy form. Publicly available docket materials are available either through 
                        <E T="03">https://www.regulations.gov</E>
                         or please contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section for additional information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Alexis Bender, Attainment Planning and Maintenance Section, Air and Radiation Division (AR18J), Environmental Protection Agency, Region 5, 77 West Jackson Boulevard, Chicago, Illinois 60604, telephone number: (312) 886-9497, email address: 
                        <E T="03">bender.alexis@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Throughout this document whenever “we,” “us,” or “our” is used, we mean the EPA.</P>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    On September 12, 2016 (81 FR 45039), the EPA designated part of St. Clair County, Michigan as nonattainment for the 2010 SO
                    <E T="52">2</E>
                     NAAQS based on modeling of the two power plant sources in the St. Clair area.
                </P>
                <P>
                    On December 15, 2023, Michigan submitted a redesignation request and maintenance plan for the St. Clair nonattainment area for the 2010 SO
                    <E T="52">2</E>
                     NAAQS to which the EPA proposed approval on April 10, 2026 (91 FR 18383). Michigan's modeled demonstration of attainment of the SO
                    <E T="52">2</E>
                     NAAQS relied upon the closure of the St. Clair Power Plant along with a Permit to Install containing permanent and enforceable SO
                    <E T="52">2</E>
                     emission limits for the Belle River Power Plant. The EPA is incorporating Belle River's Permit to Install 51-22 into Michigan's SIP in this final action. Michigan's modeling analysis demonstrates that the SO
                    <E T="52">2</E>
                     emission limits contained in Permit to Install 51-22, in combination with the St. Clair Power Plant shutdown and background concentrations, yield a maximum SO
                    <E T="52">2</E>
                     concentration of 62.8 ppb, which meets and is below the 2010 SO
                    <E T="52">2</E>
                     NAAQS of 75 ppb. The public comment period for the proposed rule ended on May 10, 2026. The EPA received no comments during the comment period.
                </P>
                <HD SOURCE="HD1">II. What action is the EPA taking?</HD>
                <P>
                    The EPA is approving the redesignation of the St. Clair area from nonattainment to attainment, meeting the criteria under CAA section 107(d)(3)(E) for the 2010 SO
                    <E T="52">2</E>
                     NAAQS in accordance with Michigan's December 15, 2023, request. The EPA is determining that the area is attaining the 2010 SO
                    <E T="52">2</E>
                     NAAQS and that the improvement in air quality is due to permanent and enforceable SO
                    <E T="52">2</E>
                     emission reductions in the area. On this basis, the EPA is approving the redesignation request from Michigan for the area and changing the legal designation of the St. Clair area at 40 CFR part 81 to attainment for the 2010 SO
                    <E T="52">2</E>
                     NAAQS. The EPA is also approving Michigan's maintenance plan under CAA section 175A. The maintenance plan demonstrates that the area will continue to maintain attainment of the 2010 SO
                    <E T="52">2</E>
                     NAAQS as the plan adequately addresses the five basic components of a maintenance plan, an attainment emissions inventory, a maintenance demonstration, a commitment for continued air quality monitoring, a process for verification of continued attainment, and a contingency plan.
                </P>
                <P>
                    Additionally, the EPA is approving into the Michigan SIP the Permit to Install 51-22, governing Belle River Power Plant SO
                    <E T="52">2</E>
                     emissions.
                </P>
                <P>In accordance with 5 U.S.C. 553(d) of the APA, this action shall become effective immediately upon publication. The immediate effective date for this action is authorized under 5 U.S.C. 553(d)(1).</P>
                <P>
                    Section 553(d)(1) of the APA provides that final rules shall not become effective until 30 days after publication in the 
                    <E T="04">Federal Register</E>
                     “except . . . a substantive rule which grants or recognizes an exemption or relieves a restriction.” The purpose of this provision is to “give affected parties a reasonable time to adjust their behavior before the final rule takes effect.” 
                    <E T="03">Omnipoint Corp.</E>
                     v. 
                    <E T="03">Fed. Commc'n Comm'n,</E>
                     78 F.3d 620, 630 (D.C. Cir. 1996); 
                    <E T="03">see also United States</E>
                     v. 
                    <E T="03">Gavrilovic,</E>
                     551 F.2d 1099, 1104 (8th Cir. 1977) (quoting legislative history). However, when the agency grants or recognizes an exemption or relieves a restriction, affected parties do not need a reasonable time to adjust because the effect is not adverse. The EPA has determined that this rule relieves a restriction because this rule relieves sources in the area of Nonattainment NSR permitting requirements; instead, upon the effective date of this action, sources will be subject to less restrictive Prevention of Significant Deterioration permitting requirements. For this reason, the EPA finds that under 5 U.S.C. 553(d)(1) it is appropriate for this action to become effective on the date of publication of this action.
                </P>
                <HD SOURCE="HD1">III. Incorporation by Reference</HD>
                <P>
                    In this rulemaking, the EPA is finalizing regulatory text that includes incorporation by reference. In accordance with requirements of 1 CFR 51.5, the EPA is finalizing the incorporation by reference of Michigan 
                    <PRTPAGE P="42357"/>
                    Permit to Install 51-22 issued to DTE Electric—Belle River Power Plant, approved April 26, 2022 and revised May 25, 2023, described in section I of this preamble and set forth in the amendments to 40 CFR part 52 below. The EPA has made, and will continue to make, these documents generally available through 
                    <E T="03">www.regulations.gov</E>
                     and at the EPA Region 5 Office (please contact the person identified in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section of this preamble for more information). Therefore, these materials have been approved by the EPA for inclusion in the SIP, have been incorporated by reference by the EPA into that plan, are fully federally enforceable under sections 110 and 113 of the CAA as of the effective date of the final rulemaking of the EPA's approval, and will be incorporated by reference in the next update to the SIP compilation.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         62 FR 27968 (May 22, 1997).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Statutory and Executive Order Reviews</HD>
                <P>Under the CAA, redesignation of an area to attainment and the accompanying approval of a maintenance plan are actions that affect the status of a geographical area and do not impose any additional regulatory requirements on sources beyond those imposed by State law. A redesignation to attainment does not in and of itself create any new requirements, but rather results in the applicability of requirements contained in the CAA for areas that have been redesignated to attainment. Moreover, the Administrator is required to approve a SIP submission that complies with the provisions of the CAA and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, the EPA's role is to approve State choices, provided that they meet the criteria of the CAA. Accordingly, this action merely approves State law as meeting Federal requirements and does not impose additional requirements beyond those imposed by State law. For these reasons, this action:</P>
                <P>• Is not a significant regulatory action subject to review by the Office of Management and Budget under Executive Order 12866 (58 FR 51735, October 4, 1993);</P>
                <P>• Is not an Executive Order 14192 (90 FR 9065, February 6, 2025) regulatory action because this action is not significant under Executive Order 12866;</P>
                <P>
                    • Does not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    );
                </P>
                <P>
                    • Is certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    );
                </P>
                <P>• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);</P>
                <P>• Does not have federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);</P>
                <P>• Is not subject to Executive Order 13045 (62 FR 19885, April 23, 1997) because it approves a State program;</P>
                <P>• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001); and</P>
                <P>• Is not subject to requirements of section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA.</P>
                <P>In addition, the SIP is not approved to apply on any Indian reservation land or in any other area where the EPA or an Indian Tribe has demonstrated that a Tribe has jurisdiction. In those areas of Indian country, the rule does not have Tribal implications and will not impose substantial direct costs on Tribal governments or preempt Tribal law as specified by Executive Order 13175 (65 FR 67249, November 9, 2000).</P>
                <P>This action is subject to the Congressional Review Act, and the EPA will submit a rule report to each House of the Congress and to the Comptroller General of the United States. This action is not a “major rule” as defined by 5 U.S.C. 804(2).</P>
                <P>Under section 307(b)(1) of the CAA, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by September 8, 2026. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this action for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. This action may not be challenged later in proceedings to enforce its requirements. (See section 307(b)(2).)</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>40 CFR Part 52</CFR>
                    <P>Environmental protection, Air pollution control, Incorporation by reference, Intergovernmental relations, Reporting and recordkeeping requirements, Sulfur oxides.</P>
                    <CFR>40 CFR Part 81</CFR>
                    <P>Environmental protection, Air pollution control, National parks, Wilderness areas.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: June 26, 2026.</DATED>
                    <NAME>Anne Vogel,</NAME>
                    <TITLE>Regional Administrator, Region 5.</TITLE>
                </SIG>
                <P>For the reasons stated in the preamble, 40 CFR parts 52 and 81 are amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 52—APPROVAL AND PROMULGATION OF IMPLEMENTATION PLANS</HD>
                </PART>
                <REGTEXT TITLE="40" PART="52">
                    <AMDPAR>1. The authority citation for part 52 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            42 U.S.C. 7401 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="52">
                    <AMDPAR>2. In § 52.1170:</AMDPAR>
                    <AMDPAR>a. Amend the table in paragraph (d) by adding an entry for “DTE Electric—Belle River Power Plant” before the entry for “DTE Energy—Trenton Channel, Wayne County”; and</AMDPAR>
                    <AMDPAR>
                        b. Amend the table in paragraph (e) under the heading “Maintenance Plans” by adding an entry for “SO
                        <E T="52">2</E>
                         (2010)” after the entry for “2010 SO
                        <E T="52">2</E>
                        ”.
                    </AMDPAR>
                    <P>The additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 52.1170</SECTNO>
                        <SUBJECT>Identification of plan.</SUBJECT>
                        <STARS/>
                        <P>(d) * * *</P>
                        <PRTPAGE P="42358"/>
                        <GPOTABLE COLS="05" OPTS="L1,nj,i1" CDEF="s50,8,r25,r50,r25">
                            <TTITLE>EPA-Approved Michigan Source-Specific Provisions</TTITLE>
                            <BOXHD>
                                <CHED H="1">Name of source</CHED>
                                <CHED H="1">Order No.</CHED>
                                <CHED H="1">
                                    State 
                                    <LI>effective date</LI>
                                </CHED>
                                <CHED H="1">EPA approval date</CHED>
                                <CHED H="1">Comments</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">DTE Electric—Belle River Power Plant</ENT>
                                <ENT>51-22</ENT>
                                <ENT>4/26/2022, revised 5/25/2023</ENT>
                                <ENT>
                                    7/9/26, 91 FR [INSERT 
                                    <E T="02">FEDERAL REGISTER</E>
                                     PAGE WHERE THE DOCUMENT BEGINS]
                                </ENT>
                                <ENT O="xl"/>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                        <P>(e) * * *</P>
                        <GPOTABLE COLS="05" OPTS="L1,nj,i1" CDEF="s50,r50,18,r50,r25">
                            <TTITLE>EPA-Approved Michigan Nonregulatory and Quasi-Regulatory Provisions</TTITLE>
                            <BOXHD>
                                <CHED H="1">
                                    Name of 
                                    <LI>nonregulatory </LI>
                                    <LI>SIP provision</LI>
                                </CHED>
                                <CHED H="1">
                                    Applicable 
                                    <LI>geographic or </LI>
                                    <LI>nonattainment </LI>
                                    <LI>area</LI>
                                </CHED>
                                <CHED H="1">
                                    State 
                                    <LI>submittal </LI>
                                    <LI>date</LI>
                                </CHED>
                                <CHED H="1">
                                    EPA 
                                    <LI>approval </LI>
                                    <LI>date</LI>
                                </CHED>
                                <CHED H="1">Comments</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW EXPSTB="04" RUL="s">
                                <ENT I="21">
                                    <E T="02">Maintenance Plans</E>
                                </ENT>
                            </ROW>
                            <ROW EXPSTB="00">
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    SO
                                    <E T="0732">2</E>
                                     (2010)
                                </ENT>
                                <ENT>St. Clair County (part)</ENT>
                                <ENT>12/14/2023 and 7/24/2025</ENT>
                                <ENT>
                                    7/9/26, 91 FR [INSERT 
                                    <E T="02">FEDERAL REGISTER</E>
                                     PAGE WHERE THE DOCUMENT BEGINS]
                                </ENT>
                                <ENT/>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 81—DESIGNATION OF AREAS FOR AIR QUALITY PLANNING PURPOSES</HD>
                </PART>
                <REGTEXT TITLE="40" PART="81">
                    <AMDPAR>3. The authority citation for part 52 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            42 U.S.C. 7401, 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="81">
                    <AMDPAR>4. In § 81.323, the table entitled “Michigan-2010 Sulfur Dioxide NAAQS [Primary]” is amended by revising the entry for “St. Clair, MI” to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 81.323 </SECTNO>
                        <SUBJECT>Michigan.</SUBJECT>
                        <STARS/>
                        <GPOTABLE COLS="03" OPTS="L1,i1" CDEF="s150,15,xs60">
                            <TTITLE>Michigan—2010 Sulfur Dioxide NAAQS</TTITLE>
                            <TDESC>[Primary]</TDESC>
                            <BOXHD>
                                <CHED H="1">
                                    Designated area 
                                    <SU>1</SU>
                                </CHED>
                                <CHED H="1">Designation</CHED>
                                <CHED H="2">
                                    Date 
                                    <SU>2</SU>
                                </CHED>
                                <CHED H="2">Type</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">St. Clair, MI</ENT>
                                <ENT>7/9/26</ENT>
                                <ENT>Attainment.</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">St. Clair County (part):  Area defined by the St. Clair River for the eastern boundary, an extension from the St. Clair River straight west to the intersection of State Highway M-29 and St. Clair River Drive, continuing west on State Highway M-29 to Church Road to Arnold Road to County Line Road for the southern boundary, County Line Road and the Macomb/St. Clair County boundary to Stoddard Road to Wales Ridge Road for the western boundary, and Alpine Road to Fitz Road to Smith Creek Road to Range Road to Huron Avenue, extending straight east from the intersection of Huron Road and River Road to the St. Clair River for the northern boundary</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <TNOTE>
                                <SU>1</SU>
                                 Includes any Indian country in each county or area, unless otherwise specified. EPA is not determining the boundaries of any area of Indian country in this table, including any area of Indian country located in the larger designation area. The inclusion of any Indian country in the designation area is not a determination that the state has regulatory authority under the Clean Air Act for such Indian country.
                            </TNOTE>
                            <TNOTE>
                                <SU>2</SU>
                                 This date is April 9, 2018, unless otherwise noted.
                            </TNOTE>
                        </GPOTABLE>
                        <PRTPAGE P="42359"/>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13843 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Parts 73 and 74</CFR>
                <DEPDOC>[MB Docket No. 24-148; FCC 25-84; FR ID 354626]</DEPDOC>
                <SUBJECT>Advancement of the Low Power Television, TV Translator and Class A Television Service</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; announcement of effective date.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In this document, the Federal Communications Commission (Commission) announces that the Office of Management and Budget has approved new information collection requirements under OMB Control Numbers 3060-0016, 3060-0466 and 3060-1216, as adopted in the Commission's Report and Order, FCC 25-84.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Amendatory instructions 11 (47 CFR 73.3700), 27 (47 CFR 74.787), 29 (47 CFR 74.791), 30 (47 CFR 74.793), and 32 (47 CFR 74.799), published at 91 FR 2861 on January 23, 2026, are effective July 9, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Cathy Williams, Office of the Managing Director, Federal Communications Commission, at (202) 418-2918 or 
                        <E T="03">Cathy.Williams@fcc.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This document announces that the Office of Management and Budget (OMB) approved the information collection requirements in 47 CFR 73.3700, 47 CFR 74.787, 47 CFR 74.791, 47 CFR 74.793 and 47 CFR 74.799 on June 26, 2026. The Commission publishes this document as an announcement of the effective date for these amended rules.</P>
                <HD SOURCE="HD1">Synopsis</HD>
                <P>As required by the Paperwork Reduction Act of 1995 (44 U.S.C. 3507), the Commission is notifying the public that it received final OMB approval on June 26, 2026, for the information collection requirements contained in 47 CFR 73.3700, 47 CFR 74.787, 47 CFR 74.791, 47 CFR 74.793 and 47 CFR 74.799. Under 5 CFR part 1320, an agency may not conduct or sponsor a collection of information unless it displays a current, valid OMB Control Number.</P>
                <P>No person shall be subject to any penalty for failing to comply with a collection of information subject to the Paperwork Reduction Act that does not display a current, valid OMB Control Number. The OMB Control Numbers for these information collections are as follows:</P>
                <P>3060-0016, 3060-0466 and 3060-1216. The foregoing notice is required by the Paperwork Reduction Act of 1995, Public Law 104-13, October 1, 1995, and 44 U.S.C. 3507.</P>
                <P>The total annual reporting burdens and costs for the respondents are as follows:</P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-0016.
                </P>
                <P>
                    <E T="03">Title:</E>
                     FCC Form 2100, Application for Media Bureau Audio and Video Service Authorization, Schedule C (Former FCC Form 346); §§ 74.793(d) and 74.787, LPTV Out-of-Core Digital Displacement Application; § 73.3700(g)(1)-(3), Post-Incentive Auction Licensing and Operations; § 74.799, Low Power Television and TV Translator Channel Sharing; § 74.720, Digital Low Power TV Distributed Transmission Systems.
                </P>
                <P>
                    <E T="03">OMB Approval Date:</E>
                     June 26, 2026.
                </P>
                <P>
                    <E T="03">OMB Expiration Date:</E>
                     June 30, 2029.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     FCC Form 2100, Schedule C.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit entities; Not-for-profit institutions; State, Local or Tribal government.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     910 respondents; 910 responses.
                </P>
                <P>
                    <E T="03">Estimated Hours per Response:</E>
                     2-2.5 hours per response.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion reporting requirement; Third party disclosure requirement.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. The statutory authority for this collection is contained in 47 U.S.C. 154(i), 303, 307, 308 and 309 of the Communications Act of 1934, as amended.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     4,090 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     $4,698,511.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     On December 19, 2025, the Commission released a Report and Order, FCC 25-84, concerning the advancement of the Class A, LPTV and TV translator services (LPTV Service). The Commission adopted a rule that provides that low power television and TV translator stations filing a displacement application (FCC Form 2100—Schedule C) include an exhibit explaining how their facilities were displaced—74.787(a). The Commission also adopted a rule providing that an LPTV or TV translator channel sharee may cease channel sharing and seek to obtain a license for a non-shared channel by filing a major modification (FCC Form 2100, Schedule C) specifying a non-shared channel and facility—74.799(i). Finally, the Commission adopted a rule—74.793—that requires that applicants seeking to construct facilities that would exceed the permissible interference levels in the rules pursuant to an agreement with the affected parties submit a copy of the agreement with their application.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-0466.
                </P>
                <P>
                    <E T="03">Title:</E>
                     §§ 74.783, 74.791, 73.1201 and 74.1283, Station Identification.
                </P>
                <P>
                    <E T="03">OMB Approval Date:</E>
                     June 26, 2026.
                </P>
                <P>
                    <E T="03">OMB Expiration Date:</E>
                     June 30, 2029.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit entities, Not-for-profit institutions; State, Local or Tribal government.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     29,146 respondents; 29,146 responses.
                </P>
                <P>
                    <E T="03">Estimated Hours per Response:</E>
                     0.166-1 hour.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion reporting requirement; Recordkeeping requirement; Third-party disclosure requirements.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     26,884 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     No costs.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. The Commission has statutory authority for the information collection requirements under 47 U.S.C. 151, 152, 154(i), 303, 307, 308.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     On December 19, 2025, the Federal Communications Commission (Commission) released a Report and Order, FCC 25-84, concerning the advancement of the Class A, LPTV and TV translator services (LPTV Service). The Commission revised its LPTV Service call sign rule—74.791 to require that stations have a call sign that is appropriate for their service designation. Stations without an appropriate call sign will be required to file a call sign change to designate a rule complaint call sign. Grandfathering of existing call signs is allowed for Class A and LPTV stations.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-1216.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Media Bureau Incentive Auction Implementation, §§ 73.3700(c), (h)(5) and (h)(6).
                </P>
                <P>
                    <E T="03">OMB Approval Date:</E>
                     June 26, 2026.
                </P>
                <P>
                    <E T="03">OMB Expiration Date:</E>
                     June 30, 2029.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit entities; Not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     1,236 respondents; 40,686 responses.
                </P>
                <P>
                    <E T="03">Estimated Hours per Response:</E>
                     .004-15 hours.
                    <PRTPAGE P="42360"/>
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     One-time reporting requirement; on occasion reporting requirement; recordkeeping requirement.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     6,570 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     $961,800.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Required to obtain or retain benefits. The Commission has statutory authority for the information collection requirements under 47 U.S.C. 151, 154, 301, 303, 307, 308, 309, 310, 316, 319, 325(b), 332, 336(f), 338, 339, 340, 399b, 403, 534, 535, 1404, 1452, and 1454.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     On December 19, 2025, the Commission released a Report and Order, FCC 25-84, concerning the advancement of the Class A, LPTV and TV translator services (LPTV Service). The Commission eliminated the requirement in § 73.3700(g)(4) that wireless licensees assigned to frequencies in the 600 MHz band under 47 CFR part 27 notify low power TV and TV translator stations of their intent to commence wireless operations and the likelihood of receiving harmful interference from the low power TV or TV translator station to such operations within the wireless licensee's licensed geographic service area.
                </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13873 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 648</CFR>
                <DEPDOC>[RTID 0648-XF489; Docket No. 260702-0161]</DEPDOC>
                <SUBJECT>Fisheries of the Northeastern United States; 2026 Chub Mackerel, Squid, and Butterfish Fishery Specifications</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>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        NMFS approves and implements specifications for the Mackerel, Squid, and Butterfish Fishery Management Plan (FMP), as recommended by the Mid-Atlantic Fishery Management Council (Council). This action sets the 2026 and projects the 2027-2028 specifications for the chub mackerel and 
                        <E T="03">Illex</E>
                         squid fisheries and reaffirms the previously projected 2026 specifications for the longfin squid and butterfish fisheries. These final specifications are intended to establish allowable harvest levels that will prevent overfishing, consistent with the most recent scientific information.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective August 10, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        A Supplemental Information Report (SIR) was prepared for this action. Copies of the SIR and other relevant environmental documentation are available upon request from Dr. Christopher M. Moore, Executive Director, Mid-Atlantic Fishery Management Council, Suite 201, 800 North State Street, Dover, DE 19901. The SIR is also accessible via the internet at: 
                        <E T="03">https://www.mafmc.org/supporting-documents.</E>
                         Copies of the small entity compliance guide are available from Michael Pentony, Regional Administrator, NMFS, Greater Atlantic Regional Fisheries Office, 55 Great Republic Drive, Gloucester, MA 01930-2298, or available on the internet at: 
                        <E T="03">https://www.greateratlantic.fisheries.noaa.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Maria Fenton, Fishery Policy Analyst, (978) 281-9196.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    NMFS manages the Atlantic mackerel, chub mackerel, 
                    <E T="03">Illex</E>
                     squid, longfin squid, and butterfish fisheries pursuant to the FMP in consultation with the Council. In 2024, the most recent year for which complete revenue data are available, this FMP supported commercial fisheries producing an overall $45.2 million in revenues. Regulations implementing the FMP appear at 50 CFR part 648, subpart B.
                </P>
                <P>Section 302(g)(1)(B) of the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act; 16 U.S.C. 1852(g)(1)(B)) states that the Scientific and Statistical Committee for each regional fishery management council shall provide its council with ongoing scientific advice for fishery management decisions, including recommendations for acceptable biological catch (ABC), preventing overfishing, ensuring maximum sustainable yield, and achieving rebuilding targets. The ABC is a level of catch that accounts for the scientific uncertainty in the estimate of the stock's defined overfishing limit (OFL).</P>
                <P>The mackerel, squid, and butterfish specifications regulations at § 648.22 require the Mackerel, Squid, and Butterfish Monitoring Committee (Monitoring Committee) to meet annually to develop specifications recommendations for each species managed under the FMP, as well as recommendations for additional management measures to assure that the specifications will not be exceeded. Specifications may be recommended for a period of up to 3 years, subject to annual review. The Mackerel, Squid, and Butterfish Committee (Committee) will review the Monitoring Committee's recommendations, as well as any public comment received on them, and develop recommendations for the Council. The Council will review the Committee's suggestions, as well as any public comments received on them, and recommend to the Regional Administrator specifications and additional measures necessary to assure that those specifications will not be exceeded.</P>
                <P>
                    During its June 2025 meeting, the Council finalized its recommendations for the 2026 and the projected 2027-2028 chub mackerel fishery specifications, and recommended reaffirming the previously projected 2026 longfin squid and butterfish fishery specifications without changes. During its August 2025 meeting, the Council finalized its recommendations for the 2026 and the projected 2027-2028 
                    <E T="03">Illex</E>
                     squid fishery specifications. Specifications for Atlantic mackerel were developed separately as part of Framework Adjustment 17 to the FMP, which was implemented by an interim final rule on April 27, 2026 (91 FR 22457).
                </P>
                <P>
                    Through this final rule, NMFS approves and implements the Council's recommended 2026 chub mackerel and 
                    <E T="03">Illex</E>
                     squid fishery specifications, projects the 2027-2028 chub mackerel and 
                    <E T="03">Illex</E>
                     squid fishery specifications, and reaffirms the previously projected 2026 longfin squid and butterfish fishery specifications. Additional background information regarding the development of these specifications was provided in the proposed rule (91 FR 12545, March 16, 2026) and is not repeated here. This rule is being issued pursuant to section 305(d) of the Magnuson-Stevens Act, which authorizes the Secretary to implement management measures necessary to carry out an approved fishery management plan. In a previous action taken pursuant to section 304(b) of the Magnuson-Stevens Act, NMFS approved the process in the FMP by which specifications are developed through a rulemaking process distinct from that of section 304(b) (76 FR 60606; Sept. 29, 2011); see the mackerel, squid, and butterfish specifications regulations at § 648.22.
                </P>
                <HD SOURCE="HD1">Final 2026 and Projected 2027-2028 Chub Mackerel Fishery Specifications</HD>
                <P>
                    Relative to the 2025 rollover specifications that are currently in 
                    <PRTPAGE P="42361"/>
                    effect, the final 2026 and projected 2027-2028 chub mackerel fishery specifications will remain status quo (table 1).
                </P>
                <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s200,13,13,13">
                    <TTITLE>Table 1—2025, Final 2026, and Projected 2027-2028 Chub Mackerel Fishery Specifications</TTITLE>
                    <TDESC>
                        [in metric tons (
                        <E T="01">mt</E>
                        )]
                    </TDESC>
                    <BOXHD>
                        <CHED H="1">Specification</CHED>
                        <CHED H="1">2025</CHED>
                        <CHED H="1">Final 2026</CHED>
                        <CHED H="1">
                            Projected
                            <LI>2027-2028</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">ABC</ENT>
                        <ENT>2,300</ENT>
                        <ENT>2,300</ENT>
                        <ENT>2,300</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Annual catch limit (ACL)</ENT>
                        <ENT>2,262</ENT>
                        <ENT>2,262</ENT>
                        <ENT>2,262</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Annual catch target (ACT)</ENT>
                        <ENT>2,171</ENT>
                        <ENT>2,171</ENT>
                        <ENT>2,171</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total allowable landings (TAL)</ENT>
                        <ENT>2,041</ENT>
                        <ENT>2,041</ENT>
                        <ENT>2,041</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Final 2026 and Projected 2027-2028 Illex Squid Fishery Specifications</HD>
                <P>
                    Relative to the 2025 rollover specifications that are currently in effect, the final 2026 and projected 2027-2028 
                    <E T="03">Illex</E>
                     squid fishery specifications will remain status quo (table 2).
                </P>
                <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s200,13,13,13">
                    <TTITLE>Table 2—2025, Final 2026, and Projected 2027-2028 Illex Squid Fishery Specifications </TTITLE>
                    <TDESC>
                        [
                        <E T="01">mt</E>
                        ]
                    </TDESC>
                    <BOXHD>
                        <CHED H="1">Specification</CHED>
                        <CHED H="1">2025</CHED>
                        <CHED H="1">Final 2026</CHED>
                        <CHED H="1">Projected 2027-2028</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">OFL</ENT>
                        <ENT>Unknown</ENT>
                        <ENT>Unknown</ENT>
                        <ENT>Unknown</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ABC</ENT>
                        <ENT>40,000</ENT>
                        <ENT>40,000</ENT>
                        <ENT>40,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Commercial discard set-aside</ENT>
                        <ENT>1,369</ENT>
                        <ENT>1,369</ENT>
                        <ENT>1,369</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Commercial discard set-aside (%)</ENT>
                        <ENT>3.42</ENT>
                        <ENT>3.42</ENT>
                        <ENT>3.42</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Initial optimum yield (IOY)</ENT>
                        <ENT>38,631</ENT>
                        <ENT>38,631</ENT>
                        <ENT>38,631</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Research set-aside (RSA) *</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Domestic annual harvest (DAH)/Domestic annual processing (DAP)</ENT>
                        <ENT>38,631</ENT>
                        <ENT>38,631</ENT>
                        <ENT>38,631</ENT>
                    </ROW>
                    <TNOTE>* The Council's RSA program has been suspended since 2014.</TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD1">Reaffirmed 2026 Longfin Squid Fishery Specifications</HD>
                <P>Relative to the 2025 rollover specifications that are currently in effect, the reaffirmed 2026 longfin squid fishery specifications will remain status quo (tables 3 and 4).</P>
                <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="s200,13,13">
                    <TTITLE>Table 3—Reaffirmed 2026 Longfin Squid Fishery Specifications </TTITLE>
                    <TDESC>
                        [
                        <E T="01">mt</E>
                        ]
                    </TDESC>
                    <BOXHD>
                        <CHED H="1">Specification</CHED>
                        <CHED H="1">2025</CHED>
                        <CHED H="1">Reaffirmed 2026</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">OFL</ENT>
                        <ENT>Unknown</ENT>
                        <ENT>Unknown</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ABC</ENT>
                        <ENT>23,400</ENT>
                        <ENT>23,400</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Commercial discard set-aside</ENT>
                        <ENT>506.3</ENT>
                        <ENT>506.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Commercial discard set-aside (%)</ENT>
                        <ENT>2.16</ENT>
                        <ENT>2.16</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">IOY</ENT>
                        <ENT>22,893.7</ENT>
                        <ENT>22,893.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RSA *</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DAH/DAP</ENT>
                        <ENT>22,893.7</ENT>
                        <ENT>22,893.7</ENT>
                    </ROW>
                    <TNOTE>*The Council's RSA program has been suspended since 2014.</TNOTE>
                </GPOTABLE>
                <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="s200,13,13">
                    <TTITLE>Table 4—Reaffirmed 2026 Longfin Squid Quota Trimester Allocations</TTITLE>
                    <BOXHD>
                        <CHED H="1">Trimester</CHED>
                        <CHED H="1">Percent of quota</CHED>
                        <CHED H="1">mt</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">I (January-April)</ENT>
                        <ENT>43</ENT>
                        <ENT>9,844.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">II (May-August)</ENT>
                        <ENT>17</ENT>
                        <ENT>3,891.9</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">III (September-December)</ENT>
                        <ENT>40</ENT>
                        <ENT>9,157.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>100</ENT>
                        <ENT>22,893.7</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="42362"/>
                <HD SOURCE="HD1">Reaffirmed 2026 Butterfish Fishery Specifications</HD>
                <P>The majority of the reaffirmed 2026 butterfish fishery specifications are lower than the 2025 rollover specifications that are currently in effect. Specifically, the ABC, ACL, and ACT are reduced by 19 percent, and the domestic annual harvest (DAH) is reduced by 29 percent. However, in recent years commercial butterfish landings have been well below the DAH and catch has been well below the ACL, so these reductions in butterfish fishery specifications are not expected to be limiting for the fishery. During 2019-2024, only 6.2-24.5 percent of the DAH and 16.8-32.3 percent of the ACL was harvested annually, which resulted in annual landings ranging from 718 to 3,442 mt and annual catch ranging from 3,874 to 5,394 mt (tables 5 and 6).</P>
                <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="s200,13,13">
                    <TTITLE>Table 5—Reaffirmed 2026 Butterfish Fishery Specifications </TTITLE>
                    <TDESC>
                        [
                        <E T="01">mt</E>
                        ]
                    </TDESC>
                    <BOXHD>
                        <CHED H="1">Specification</CHED>
                        <CHED H="1">2025</CHED>
                        <CHED H="1">
                            Reaffirmed
                            <LI>2026</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">OFL</ENT>
                        <ENT>17,587</ENT>
                        <ENT>14,224</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ABC/ACL</ENT>
                        <ENT>17,115</ENT>
                        <ENT>13,842</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ACT buffer</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ACT buffer (%)</ENT>
                        <ENT>0 (%)</ENT>
                        <ENT>0 (%)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ACT</ENT>
                        <ENT>17,115</ENT>
                        <ENT>13,842</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">RSA *</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total allowable level of foreign fishing</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Butterfish cap in longfin squid fishery</ENT>
                        <ENT>3,884</ENT>
                        <ENT>3,884</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Assumed other discards</ENT>
                        <ENT>1,907</ENT>
                        <ENT>1,907</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total discard set-aside (all sources)</ENT>
                        <ENT>5,791</ENT>
                        <ENT>5,791</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DAH/DAP</ENT>
                        <ENT>11,324</ENT>
                        <ENT>8,051</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Closure threshold (amount caught)</ENT>
                        <ENT>10,324</ENT>
                        <ENT>7,051</ENT>
                    </ROW>
                    <TNOTE>* The Council's RSA program has been suspended since 2014.</TNOTE>
                </GPOTABLE>
                <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="s200,13,13">
                    <TTITLE>Table 6—Reaffirmed 2026 Allocation of the Butterfish Mortality Cap</TTITLE>
                    <BOXHD>
                        <CHED H="1">Trimester</CHED>
                        <CHED H="1">Percent</CHED>
                        <CHED H="1">
                            Metric
                            <LI>tons</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">I (January-April)</ENT>
                        <ENT>43</ENT>
                        <ENT>1,670</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">II (May-August)</ENT>
                        <ENT>17</ENT>
                        <ENT>660</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">III (September-December)</ENT>
                        <ENT>40</ENT>
                        <ENT>1,554</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>100</ENT>
                        <ENT>3,884</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Comments and Responses</HD>
                <P>NMFS published a proposed rule on March 16, 2026 (91 FR 12545), and the public comment period ended on April 15, 2026. We received one comment from a member of the public during the comment period, but it did not mention anything specific to the measures contained in the action.</P>
                <HD SOURCE="HD1">Changes From the Proposed Rule</HD>
                <P>There are no changes from the proposed rule.</P>
                <HD SOURCE="HD1">Classification</HD>
                <P>NMFS is issuing this rule pursuant to section 305(d) of the Magnuson Stevens Act (16 U.S.C. 1855(d)). In a previous action taken pursuant to section 304(b) of the Magnuson-Stevens Act (16 U.S.C. 1854(b)), the FMP and implementing regulations created the process by which specifications are developed through a NMFS rulemaking process distinct from that of 304(b) (76 FR 60606; Sept. 29, 2011). See the mackerel, squid, and butterfish specifications regulation at § 648.22. The NMFS Assistant Administrator has determined that this final rule is consistent with the FMP, other provisions of the Magnuson-Stevens Act, and other applicable laws.</P>
                <P>This final rule is exempt from review under Executive Order (E.O.) 12866.</P>
                <P>This rule is not an E.O. 14192 regulatory action because this rule is not significant under E.O. 12866.</P>
                <P>NMFS has determined that this action 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; therefore, consultation with Tribal officials under E.O. 13175 is not required, and the requirements of section (5)(b) and (c) of E.O. 13175 also do not apply. A Tribal summary impact statement under section (5)(b)(2)(B) and (c)(2)(B) of E.O. 13175 is not required and has not been prepared.</P>
                <P>The Chief Counsel for Regulation of the Department of Commerce certified to the Chief Counsel for Advocacy of the Small Business Administration during the proposed rule stage that this action would not have a significant economic impact on a substantial number of small entities. The factual basis for this certification was published in the proposed rule and is not repeated here. No comments were received regarding this certification. As a result, a final regulatory flexibility analysis was not required and none was prepared.</P>
                <P>This final 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. 1801 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Samuel D. Rauch III,</NAME>
                    <TITLE>Deputy Assistant Administrator for Regulatory Programs, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13867 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>91</VOL>
    <NO>130</NO>
    <DATE>Thursday, July 9, 2026</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="42363"/>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <CFR>12 CFR Part 208</CFR>
                <DEPDOC>[Docket No. R-1835]</DEPDOC>
                <RIN>RIN 7100-AG78</RIN>
                <SUBJECT>Anti-Money Laundering and Countering the Financing of Terrorism Programs</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>The Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Board of Governors of the Federal Reserve System (the Board) is inviting comment on a proposed rule that would require its supervised banks to establish and maintain effective anti-money laundering and countering the financing of terrorism (AML/CFT) programs reasonably designed to identify, assess, and mitigate risks of illicit finance. Among other changes, this proposed rule would ensure that Board-supervised banks establish and maintain effective AML/CFT programs that are intended to better achieve the purposes of the Bank Secrecy Act (BSA), culminating in the development of highly useful information related to illicit financial transactions for law enforcement and national security agencies. The amendments are intended to align with changes to AML/CFT program requirements proposed by the Financial Crimes Enforcement Network (FinCEN) to implement provisions of the Anti-Money Laundering Act of 2020 (AML Act) and corresponding changes proposed by the Office of the Comptroller of the Currency (OCC), Federal Deposit Insurance Corporation (FDIC), and the National Credit Union Administration (NCUA) (collectively, “the Agencies”) on April 10, 2026.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 8, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by Docket No. R-1835 and RIN 7100-AG78, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Agency Website: https://www.federalreserve.gov/apps/proposals/.</E>
                         Follow the instructions for submitting comments, including attachments. 
                        <E T="03">Preferred Method.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Benjamin W. McDonough, Secretary, Board of Governors of the Federal Reserve System, 20th Street and Constitution Avenue NW, Washington, DC 20551.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Same as mailing address.
                    </P>
                    <P>
                        • 
                        <E T="03">Other Means: publiccomments@frb.gov.</E>
                         You must include Docket No. R-1835 and RIN 7100-AG78 in the subject line of the message.
                    </P>
                    <P>
                        Comments received are subject to public disclosure. In general, comments received will be made available on the Board's website at 
                        <E T="03">https://www.federalreserve.gov/apps/proposals/</E>
                         without change and will not be modified to remove personal or business information including confidential, contact, or other identifying information. Comments should not include any information such as confidential information that would not be appropriate for public disclosure. Public comments may also be viewed electronically or in person in Room M-4365A, 2001 C St. NW, Washington, DC 20551, between 9 a.m. and 5 p.m. during Federal business weekdays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Lara Lylozian, Deputy Associate Director, (202) 815-9088, 
                        <E T="03">lara.k.lylozian@frb.gov,</E>
                         Lee Davis, Lead BSA/AML Policy Analyst, (202) 740-8219, 
                        <E T="03">lee.h.davis@frb.gov,</E>
                         Division of Supervision and Regulation; or Jason Gonzalez, Deputy Associate General Counsel, (202) 452-3275, 
                        <E T="03">jason.a.gonzalez@frb.gov,</E>
                         Bernard Kim, Senior Special Counsel, (202) 452-3083, 
                        <E T="03">bernard.g.kim@frb.gov,</E>
                         Darien Capron, Senior Counsel, (202) 304-2531, 
                        <E T="03">darien.s.capron@frb.gov,</E>
                         Legal Division, Board of Governors of the Federal Reserve System, 20th and C Streets NW, Washington, DC 20551. For users of TDD-TYY, (202) 263-4869 or dial 711 from any telephone anywhere in the United States.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Scope</HD>
                <P>
                    The proposed rule would amend the Board's regulations that prescribe AML/CFT program requirements 
                    <SU>1</SU>
                    <FTREF/>
                     for banks 
                    <SU>2</SU>
                    <FTREF/>
                     supervised by the Board in a way that aligns with the rules proposed by FinCEN and the Agencies 
                    <SU>3</SU>
                    <FTREF/>
                     under the BSA on April 10, 2026.
                    <SU>4</SU>
                    <FTREF/>
                     While FinCEN has delegated its authority to examine Board-supervised banks for compliance with the BSA to the Board, the Board also has independent authority to prescribe regulations requiring banks to establish and maintain procedures reasonably designed to assure and monitor their compliance with the requirements of subchapter II of chapter 53 of title 31, under 12 U.S.C. 1818(s) (Section 8(s) of the Federal Deposit Insurance Act). The Board is proposing to amend its rules to align with FinCEN and the Agencies so that its program requirements for Board-supervised banks remain consistent with those imposed by FinCEN and the Agencies. Further, with consistent regulatory text, banks will not be subject to any additional burden or confusion from needing to comply with differing standards between regulatory agencies. The proposed changes are discussed in more detail below in the section-by-section analysis.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         In Section IV.A., the Board describes the express incorporation of the countering the financing of terrorism (CFT) requirements as part of a bank's anti-money laundering (AML) program requirements. For consistency throughout this proposed rule, AML program requirements will be described as AML/CFT program requirements.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The term “bank” is defined in regulations implementing the BSA, 31 CFR 1010.100(d), and includes each agent, agency, branch, or office within the United States of banks, savings associations, credit unions, and foreign banks.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         FinCEN and the Agencies are separately requesting comment on proposed amendments to their AML/CFT Program Rules for banks. 
                        <E T="03">See</E>
                         91 FR 18704 (Apr.10, 2026) and 91 FR 18304 (Apr. 10, 2026). FinCEN, the Board, and the Agencies each have their own implementing regulations. 
                        <E T="03">See</E>
                         31 CFR 1020.210 (FinCEN); 12 CFR 208.63 (Board); 12 CFR 21.21 (OCC); 12 CFR 326.8 (FDIC); and 12 CFR 748.2 (NCUA).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         FinCEN currently defines the term “Bank Secrecy Act” in 31 CFR 1010.100(e). However, FinCEN's proposed rule also would make minor changes to the definitions in FinCEN regulations. These changes include the definition of “Bank Secrecy Act” at 31 CFR 1010.100(e), adding statutory references to the Anti-Money Laundering Act of 2020 (AML Act) and the Corporate Transparency Act, and removing the reference to “collection of statutes commonly referred to as. . . .” Certain criminal statutes—namely, 18 U.S.C. 1956, 1957, and 1960—are currently included in the BSA definition at 31 CFR 1010.100(e). Section 6003 of the AML Act, however, does not include these provisions in its BSA definition, and thus FinCEN is not considering them part of the BSA for the purposes of its proposed rule.
                    </P>
                </FTNT>
                <PRTPAGE P="42364"/>
                <HD SOURCE="HD1">II. Background</HD>
                <HD SOURCE="HD2">A. Anti-Money Laundering Programs Under the Bank Secrecy Act and History of the BSA Compliance Program Rules for the Board and the Agencies</HD>
                <P>
                    Enacted in 1970 and amended several times since, the BSA is designed to combat money laundering, the financing of terrorism, and other illicit finance activity risks (collectively, ML/TF risks).
                    <SU>5</SU>
                    <FTREF/>
                     Congress has authorized the Secretary of the Treasury (Secretary) to administer the BSA. The Secretary has in turn delegated the authority to implement, administer, and enforce compliance with the BSA and its associated regulations to the Director of FinCEN (FinCEN Director).
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         31 U.S.C. 5311(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Treasury Order 180-01 (Jan. 14, 2020), paragraph 3; 
                        <E T="03">see also</E>
                         31 U.S.C. 310(b)(2)(I) (providing that the Director of FinCEN shall “[a]dminister the requirements of subchapter II of chapter 53 of this title, chapter 2 of title I of Public Law 91-508, and section 21 of the Federal Deposit Insurance Act, to the extent delegated such authority by the Secretary of the Treasury.”).
                    </P>
                </FTNT>
                <P>
                    The Money Laundering Control Act of 1986 (MLCA) 
                    <SU>7</SU>
                    <FTREF/>
                     amended 12 U.S.C. 1818(s) and 12 U.S.C. 1786(q) (Sections 8(s) of the Federal Deposit Insurance Act and 206(q) of the Federal Credit Union Act, respectively) to require the Board and the Agencies to issue regulations requiring their supervised banks to “establish and maintain procedures reasonably designed to assure and monitor their compliance” of their supervised banks with the requirements of the BSA. Consistent with the MLCA, on January 27, 1987, all the then-Federal bank regulatory agencies issued substantially similar regulations requiring their supervised banks to develop procedures for BSA compliance.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Public Law 99-570,  5318, 100 Stat. 3207, 3207-29 (1986).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         52 FR 2858 (Jan. 27, 1987).
                    </P>
                </FTNT>
                <P>
                    Since its original enactment, Congress has continued to address various aspects of AML/CFT compliance, including through expansion of the BSA.
                    <SU>9</SU>
                    <FTREF/>
                     In 1992, the Annunzio-Wylie Anti-Money Laundering Act 
                    <SU>10</SU>
                    <FTREF/>
                     gave the Secretary authority to prescribe minimum standards for AML programs, including: “(A) the development of internal policies, procedures, and controls, (B) the designation of a compliance officer, (C) an ongoing employee training program, and (D) an independent audit function to test programs”—what are often called the “four pillars” of AML/CFT programs.
                    <SU>11</SU>
                    <FTREF/>
                     Later, the Uniting and Strengthening America by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism Act of 2001 (USA PATRIOT Act) further amended the BSA to include, among other things, customer identification program (CIP) requirements and the expansion of AML program rules to cover certain other financial industry participants (
                    <E T="03">e.g.,</E>
                     credit unions and futures commission merchants).
                    <SU>12</SU>
                    <FTREF/>
                     The USA PATRIOT Act also made it mandatory for financial institutions to maintain AML programs that meet minimum prescribed standards.
                    <SU>13</SU>
                    <FTREF/>
                     Through the exercise of its delegated authority, FinCEN is authorized to require each financial institution to establish an AML/CFT program to ensure compliance with the BSA and guard against ML/TF risks.
                    <SU>14</SU>
                    <FTREF/>
                     Over time, FinCEN, the Board, and the Agencies incorporated many of these standards into their respective program rules, and FinCEN implemented additional requirements for certain covered financial institutions into their respective program rules.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Most recently, Congress enacted the Guiding and Establishing National Innovation for U.S. Stablecoins (GENIUS) Act on July 18, 2025. Pub. L. 119-27, 
                        <E T="03">codified at</E>
                         12 U.S.C. 5901 
                        <E T="03">et seq.</E>
                         The GENIUS Act requires that permitted payment stablecoin issuers (PPSIs) be treated as financial institutions under the BSA, including being required to maintain “an effective anti-money laundering program.” 
                        <E T="03">See</E>
                         12 U.S.C. 5903(a)(5)(i). The GENIUS Act also requires the Board and the Agencies to issue regulations relating to PPSIs, including Bank Secrecy Act and sanctions compliance standards. These AML/CFT standards for PPSIs will be addressed separately from this rulemaking.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Section 1517 of the Annunzio-Wylie Anti-Money Laundering Act, Public Law 102-550, 106 Stat. 3672 (Oct. 28, 1992) (Annunzio-Wylie).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         31 U.S.C. 5318(h)(1), as added by section 1517(b) of Annunzio-Wylie. The proposed rule modifies the current sequencing of AML/CFT program components; however, the change in sequencing is not intended to modify or signify changes in any substantive requirements.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         31 U.S.C. 5312(a)(2)(E) and 31 U.S.C. 5312(c), as added by section 321 of the USA PATRIOT Act, Public Law 107-56, 115 Stat. 272 (Oct. 26, 2001) (USA PATRIOT).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         31 U.S.C. 5318(h), as added by section 352 of USA PATRIOT.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         31 U.S.C. 5318(a)(2), (h)(1), and (h)(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         FinCEN, 
                        <E T="03">Customer Due Diligence Requirements for Financial Institutions,</E>
                         81 FR 29398 (May 11, 2016).
                    </P>
                </FTNT>
                <P>Although in practice the FinCEN AML program rule and the Board's compliance program rule for banks operate together, since the USA PATRIOT Act, banks have been required to maintain compliance programs under separate legal authorities administered by (i) FinCEN under Title 31 and (ii) the Board under Section 8(s). Because the authority for the Board's BSA compliance program rule derives from and is required by Section 8(s), the Board prescribed regulations requiring the banks they supervise to establish and maintain procedures reasonably designed to assure and monitor the compliance of such banks with the requirements of the BSA.</P>
                <P>
                    In 2003, FinCEN, the Board, the Agencies, the Securities and Exchange Commission, and the Commodity Futures Trading Commission jointly issued final rules on CIP requirements,
                    <SU>16</SU>
                    <FTREF/>
                     which were mandated by amendments to the BSA under the USA PATRIOT Act requiring financial institutions to implement a CIP as part of their BSA compliance program.
                    <SU>17</SU>
                    <FTREF/>
                     The CIP requirements became part of the separate AML program rules for banks administered by FinCEN, the Board, and the Agencies, although the rules continued to function together by allowing banks to satisfy FinCEN's rule by complying with their supervising agency's rule.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         68 FR 25090 (May 9, 2003).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         31 U.S.C. 5318(l), as added by section 326 of USA PATRIOT.
                    </P>
                </FTNT>
                <P>
                    In 2016, FinCEN amended its AML compliance program rules to incorporate customer due diligence (CDD) requirements, including beneficial ownership information collection requirements for certain covered financial institutions, including banks.
                    <SU>18</SU>
                    <FTREF/>
                     Although the Board and the Agencies did not promulgate CDD requirements at that time, the agencies examine their supervised banks for compliance with those requirements under the authority of Sections 8(s) and 206(q).
                    <SU>19</SU>
                    <FTREF/>
                     With the exception of the CDD requirement, FinCEN's rule was substantially similar to the rules of the Agencies and the Board, and banks must currently comply with both FinCEN's AML bank program rule and the BSA compliance rules of the Board or the Agencies, as appropriate.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         81 FR 29398 (May 11, 2016).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         Press Release, Joint Statement on Enforcement of Bank Secrecy Act/Anti-Money Laundering Requirements (Aug. 13, 2020), 
                        <E T="03">https://www.federalreserve.gov/newsevents/pressreleases/files/bcreg20200813a1.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. The Anti-Money Laundering Act of 2020</HD>
                <P>
                    On January 1, 2021, Congress enacted the William M. (Mac) Thornberry National Defense Authorization Act for Fiscal Year 2021, of which the AML Act was a component.
                    <SU>20</SU>
                    <FTREF/>
                     With the passage of the AML Act, Congress stated that it was seeking to modernize and strengthen the AML/CFT regulatory framework, which “had not seen comprehensive reform or modernization” since the BSA was 
                    <PRTPAGE P="42365"/>
                    enacted in the 1970s.
                    <SU>21</SU>
                    <FTREF/>
                     Among other objectives, Congress intended for the AML Act to require “more routine and systemic coordination, communication, and feedback among financial institutions, regulators, and law enforcement to identify suspicious financial activities, better focusing bank resources to the AML task, which will increase the likelihood for better law enforcement outcomes.” 
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         William M. (Mac) Thornberry National Defense Authorization Act for Fiscal Year 2021, Public Law 116-283, 134 Stat. 3388 (Jan. 1, 2021).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Congress noted in its Joint Explanatory Statement (JES) of the Committee of Conference accompanying the FY21 NDAA that: “the current [AML/CFT] regulatory framework is an amalgamation of statutes and regulations that are grounded in the [BSA], which the Congress enacted in 1970. This decades-old regime, which has not seen comprehensive reform and modernization since its inception, is generally built on individual reporting mechanisms (
                        <E T="03">i.e.,</E>
                         currency transaction reports (CTRs) and suspicious activity reports (SARs)) and contemplates aging, decades-old technology, rather than the current, sophisticated AML compliance systems now managed by most financial institutions.” Congress further stated that the AML Act “comprehensively update[s] the BSA for the first time in decades and provide[s] for the establishment of a coherent set of risk-based priorities.” Among other objectives, Congress intended for the AML Act to require “more routine and systemic coordination, communication, and feedback among financial institutions, regulators, and law enforcement to identify suspicious financial activities, better focusing bank resources to the AML task, which will increase the likelihood for better law enforcement outcomes.” H.R. Rep. No. 6395 (2020) at pp. 731-732 (Joint Explanatory Statement of the Committee of Conference) (
                        <E T="03">https://docs.house.gov/billsthisweek/20201207/116hrpt617-JointExplanatoryStatement.pdf</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         H.R. Rep. No. 6395 (2020) at 732 (Joint Explanatory Statement of the Committee of Conference).
                    </P>
                </FTNT>
                <P>Section 6101(b) of the AML Act made several changes to the BSA's AML/CFT program requirements.</P>
                <P>First, section 6101(b) amended the BSA at 31 U.S.C. 5318(h)(2)(B) to state that, “[i]n prescribing the minimum standards for [AML/CFT programs], and in supervising and examining compliance with those standards, the Secretary of the Treasury, and the appropriate Federal functional regulator (as defined in section 509 of the Gramm-Leach-Bliley Act (15 U.S.C. 6809)) shall take into account” certain factors.</P>
                <P>
                    Second, section 6101(b) requires the Secretary, in consultation with the Attorney General, appropriate Federal functional regulators, relevant State financial regulators, and relevant national security agencies, to establish and make public government-wide AML/CFT priorities (AML/CFT Priorities). After consultation with the Federal functional regulators and relevant State financial regulators, the Secretary must promulgate regulations, as appropriate, to incorporate those priorities into revised program rules, and incorporation of the priorities must be included as a measure on which financial institutions are supervised and examined. FinCEN issued the first AML/CFT Priorities on June 30, 2021.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         AML/CFT Priorities (June 30, 2021). As required by 31 U.S.C. 5318(h)(4)(C), the AML/CFT Priorities are consistent with Treasury's National Strategy for Combating Terrorist and Other Illicit Financing (May 16, 2024). The AML/CFT Priorities are supported by Treasury's National Risk Assessments on Money Laundering, Terrorist Financing, and Proliferation Financing (Mar. 2026)). Additionally, Treasury is required to consult with the Board and the Agencies on the National Illicit Finance Strategy, which must include a risk assessment. 
                        <E T="03">See</E>
                         Combating Terrorism and Illicit Financing, Public Law 115-44, 131 Stat. 934 (2017). As also required by 31 U.S.C. 5318(h)(4)(B), the Secretary, in consultation with the Attorney General, Federal functional regulators, relevant State financial regulators, and relevant national security agencies, must update the AML/CFT Priorities not less frequently than once every four years.
                    </P>
                </FTNT>
                <P>Third, section 6101(b) expands the BSA's program rule requirement to formally include an express reference to CFT in addition to AML.</P>
                <P>Fourth, section 6101(b) provides that the duty to establish, maintain, and enforce an AML/CFT program shall remain the responsibility of, and be performed by, persons in the United States who are accessible to, and subject to oversight and supervision by, the Secretary and the appropriate Federal functional regulator.</P>
                <HD SOURCE="HD2">C. Prior BSA Modernization Efforts</HD>
                <P>The proposed rule also builds upon other recent efforts by FinCEN, the Board, and the Agencies to modernize AML/CFT compliance program requirements for banks, both before and after the passage of the AML Act. These efforts include actions taken to revise the BSA regulatory regime through rulemakings, providing exemptive relief from regulatory requirements consistent with the purposes of the BSA, and clarifying regulatory requirements and supervisory standards through policy documents.</P>
                <P>
                    For example, on July 22, 2019, FinCEN, the Board, and the Agencies issued a joint statement to clarify and explain their existing risk-focused approach to examinations of banks' BSA/AML compliance programs. This statement was intended to increase transparency into the risk-focused approach used by the Board and the Agencies for planning and performing BSA/AML examinations, which included clarifying that the Board and the Agencies “generally allocate more resources to higher-risk areas, and fewer resources to lower-risk areas” based on the bank's unique risk profile.
                    <SU>24</SU>
                    <FTREF/>
                     FinCEN, the Board, and the Agencies have also taken steps to highlight that customer relationships present varying levels of ML/TF risk and, in turn, to encourage banks to manage customer relationships and mitigate risks based on customer relationships, rather than decline to provide banking services to entire categories of customers.
                    <SU>25</SU>
                    <FTREF/>
                     More recently, the Board and the Agencies have, with FinCEN's concurrence, issued an order permitting banks, as part of their CIP obligations, to collect Taxpayer Identification Number information from a third party rather than directly from the bank's customer, subject to certain conditions.
                    <SU>26</SU>
                    <FTREF/>
                     FinCEN, the Board, and the Agencies have also issued Frequently Asked Questions to clarify certain obligations related to filing a suspicious activity report (SAR) to help ensure banks are not needlessly expending resources on efforts that do not provide law enforcement and national security agencies with the critical information they need to detect, combat, and deter criminal activity, as well as to combat misconceptions that banks are required to terminate customer relationships based on the filing of a SAR.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See</E>
                         Board SR letter 19-11, Joint Statement on the Risk-Focused Approach to BSA/AML Supervision (July 22, 2019), 
                        <E T="03">https://www.federalreserve.gov/supervisionreg/srletters/sr1911.htm.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Joint Statement on the Risk-Based Approach to Assessing Customer Relationships and Conducting Customer Due Diligence (July 6, 2022) (“Customer relationships present varying levels of money laundering, terrorist financing, and other illicit financial activity risks. The potential risk to a bank depends on the presence or absence of numerous factors, including facts and circumstances specific to the customer relationship. The [Board and the] Agencies continue to encourage banks to manage customer relationships and mitigate risks based on customer relationships, rather than decline to provide banking services to entire categories of customers.”)
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See</E>
                         OCC, FDIC, NCUA, FinCEN, 
                        <E T="03">Agencies Issue Exemption Order to Customer Identification Program Requirements,</E>
                         (Jun. 27, 2025), 
                        <E T="03">https://www.occ.gov/news-issuances/news-releases/2025/nr-ia-2025-60.html,</E>
                         and Board SR Letter 25-2, Order Granting an Exemption from the Customer Identification Program Rule Requirement Related to a Bank Obtaining Taxpayer Identification Number Information from the Customer, (August 15, 2025), 
                        <E T="03">https://www.federalreserve.gov/supervisionreg/srletters/SR2502.htm.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         FinCEN et. al, 
                        <E T="03">Answers to Frequently Asked Questions Regarding Suspicious Activity Reporting and Other Anti-Money Laundering Considerations</E>
                         (Jan. 19, 2021) (clarifying, among other things, that there is no BSA regulatory requirement to terminate a customer relationship after the filing of a SAR or any specific number of SARs). 
                        <E T="03">See also</E>
                         FinCEN et. al, 
                        <E T="03">Frequently Asked Questions Regarding Suspicious Activity Reporting Requirements</E>
                         (Oct. 9, 2025), 
                        <E T="03">https://www.fincen.gov/system/files/2025-10/SAR-FAQs-October-2025.pdf</E>
                         (clarifying filing requirements related to potential structuring-related activity, documentation requirements related to not filing a SAR on potentially suspicious activity, and certain aspects of continuing activity reporting).
                    </P>
                </FTNT>
                <P>
                    With respect to prior rulemaking efforts, prior to the enactment of the AML Act, FinCEN published an ANPRM seeking public comment on 
                    <PRTPAGE P="42366"/>
                    potential regulatory amendments intended to increase the effectiveness of program rule requirements (Effectiveness ANPRM), which was informed by recommendations of the AML Effectiveness Bank Secrecy Act Advisory Group working group.
                    <SU>28</SU>
                    <FTREF/>
                     While the Effectiveness ANPRM was issued by FinCEN on a standalone basis, the Board and the Agencies were consultative partners with FinCEN when developing the proposal. More recently, on July 3, 2024, FinCEN published an NPRM proposing revisions to its AML/CFT program requirements for all financial institutions, including those applicable to banks,
                    <SU>29</SU>
                    <FTREF/>
                     and on August 9, 2024, the Board and the Agencies issued an NPRM proposing substantially similar amendments to their respective AML program rules applicable to banks they supervise (the 2024 Program NPRM).
                    <SU>30</SU>
                    <FTREF/>
                     These proposed rules were never finalized.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         FinCEN, 
                        <E T="03">Anti-Money Laundering Program Effectiveness,</E>
                         85 FR 58023 (Sept. 17, 2020).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         FinCEN, 
                        <E T="03">Anti-Money Laundering and Countering the Financing of Terrorism Requirements,</E>
                         89 FR 55428 (Jul. 3, 2024).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         OCC, Board, FDIC and the NCUA, 
                        <E T="03">Anti-Money Laundering and Countering the Financing of Terrorism Requirements,</E>
                         89 FR 65242 (Aug. 9, 2024).
                    </P>
                </FTNT>
                <P>
                    In proposing this rule in coordination with FinCEN and the Agencies, the Board considered applicable statutory requirements and prior feedback on these recent BSA modernization efforts, including comments provided on FinCEN's Effectiveness ANPRM and those received by FinCEN, the Board, and the Agencies on the 2024 Program NPRM. While building upon these prior modernization efforts, the proposed rule is distinct and separate from prior BSA modernization rulemaking efforts.
                    <SU>31</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         For an overview of the content of the Effectiveness ANPRM and the 2024 Program NPRM, and for an overview of comments received on both, refer to FinCEN's proposed revisions to its AML/CFT program requirements, issued on April 10, 2026. 
                        <E T="03">See</E>
                         91 FR 18704 (Apr.10, 2026).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Overview of the Proposed Rule</HD>
                <P>
                    A central objective of the Board's and the Agencies' BSA modernization efforts is to create an AML/CFT supervisory and regulatory regime that is more effective in achieving the purposes of the BSA and culminating in the development of highly useful information related to illicit financial transactions for law enforcement and national security agencies.
                    <SU>32</SU>
                    <FTREF/>
                     The proposed rule would further that objective by explicitly defining the requirements for a bank to establish and maintain an effective AML/CFT program. It would also adopt into regulations the AML Act's expectation that AML/CFT programs should be risk-based, including ensuring that banks direct more attention and resources toward higher-risk customers and activities, consistent with the risk profile of the bank, rather than toward lower-risk customers and activities.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         31 U.S.C. 5311.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         31 U.S.C. 5318(h)(2).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. Proposed Rule</HD>
                <P>
                    As noted above, the proposed rule would require Board-supervised banks to establish and maintain effective AML/CFT programs and define the requirements for doing so. In order for an AML/CFT program to be effective, the proposed rule would require a Board-supervised bank to 
                    <E T="03">establish</E>
                     an AML/CFT program and then 
                    <E T="03">maintain</E>
                     the AML/CFT program by implementing, in all material respects, the established AML/CFT program.
                </P>
                <P>As described in more detail in section IV.D, a Board-supervised bank would be required to establish a risk-based set of internal policies, procedures, and controls that is reasonably designed to ensure compliance with the BSA and its implementing regulations, 31 CFR chapter X. The risk-based set of internal policies, procedures, and controls must also be reasonably designed to (1) identify, assess, and document the bank's ML/TF risks through risk assessment processes that evaluate the risks of the bank's business activities, review and, as appropriate, incorporate the AML/CFT Priorities, and are updated promptly upon any change that the bank knows or has reason to know significantly changes the bank's ML/TF risks; (2) mitigate the bank's ML/TF risks consistent with the bank's risk assessment processes including by directing more attention and resources toward higher-risk customers and activities, rather than toward lower-risk customers and activities; and (3) conduct ongoing customer due diligence.</P>
                <P>The proposed rule would also require a Board-supervised bank to establish an ongoing employee training program and independent AML/CFT program testing as part of its AML/CFT program. Finally, the proposed rule would require a Board-supervised bank to designate an individual responsible for establishing and implementing the AML/CFT program and coordinating and monitoring day-to-day compliance; that individual would be required to be located in the United States and accessible to, and subject to oversight and supervision by, FinCEN or its designee and the Board.</P>
                <P>
                    Under the proposed rule, in addition to establishing an AML/CFT program, the bank would be required to maintain that program by 
                    <E T="03">implementing,</E>
                     in all material respects, its established AML/CFT program. By structuring the requirement to have an effective AML/CFT program as distinct obligations to establish and maintain (via implementation) an AML/CFT program, the proposed rule is intended to clarify and reinforce the distinction between failures to establish an AML/CFT program and failures to implement a properly established program.
                </P>
                <P>
                    The distinction between establishing a program and maintaining a program by implementing it in all material respects is particularly important under the proposed rule for potential supervisory and enforcement actions. The proposed rule would not limit enforcement or supervisory actions for failures to 
                    <E T="03">establish</E>
                     an AML/CFT program. However, once a Board-supervised bank has properly established an AML/CFT program, the proposed rule would raise the threshold for significant supervisory or enforcement actions based solely on 
                    <E T="03">implementation</E>
                     deficiencies. Only significant or systemic failures by a bank to implement in all material respects an established program would warrant an “AML/CFT enforcement action” or a “significant AML/CFT supervisory action,” as these terms are defined in the proposed rule. In this way, the proposed rule is intended to clarify and reinforce a supervisory and enforcement focus on addressing significant or systemic failures to implement a properly established AML/CFT program, rather than on isolated, technical, or immaterial implementation issues.
                    <SU>34</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         Board, FDIC, NCUA, OCC, 
                        <E T="03">Joint Statement on Enforcement of Bank Secrecy Act/Anti-Money Laundering Requirements,</E>
                         (Aug. 13, 2020), 
                        <E T="03">https://www.federalreserve.gov/frrs/regulations/statement-on-bank-secrecy-act-anti-money-laundering-enforcement.htm.</E>
                    </P>
                </FTNT>
                <P>
                    Importantly, under the proposed regulations, having an effective AML/CFT program would be more than a one-time adoption of a risk-based set of internal policies, procedures, and controls. Rather, a Board-supervised bank would be required to keep its risk-based set of internal policies, procedures, and controls—and the risk assessment processes that inform them—current as the bank's risk profile changes. For example, while a bank's risk-based set of internal policies, procedures, and controls may, at one time, have been reasonably designed, they may no longer be reasonably designed given changes to the bank's 
                    <PRTPAGE P="42367"/>
                    risk profile. Similarly, an AML/CFT program would be more than a one-time creation of an employee training program or initiation of an independent testing mechanism: the bank would be required to keep such aspects of the AML/CFT program current as the bank's risk profile changes. Thus, even where a Board-supervised bank has previously established an AML/CFT program in accordance with the proposed rule, a failure to update the program to reflect significant changes in the bank's risk profile may result in the program no longer meeting the program establishment requirements, and the bank may accordingly be subject to supervisory or enforcement action for a failure to establish an effective AML/CFT program.
                </P>
                <P>By explicitly defining the requirements for a bank to establish and maintain an effective AML/CFT program, and by standardizing the AML/CFT supervision and enforcement policy for banks and across the Board and the Agencies, the proposed rule is expected to better achieve the purposes of the BSA, culminating in the development of highly useful information related to illicit financial transactions for banks and law enforcement and national security agencies. However, the Board does not intend for the proposed rule to provide banks permission to establish an AML/CFT program that might be interpreted as meeting the proposed rule's technical requirements on their face, but do not effectively detect and prevent ML/TF activity. To establish a compliant AML/CFT program under the proposed rule, a Board-supervised bank must, among other things, establish a risk-based set of internal policies, procedures, and controls that is reasonably designed to ensure compliance with the BSA and 31 CFR chapter X, including through the adoption of risk assessment processes. A critical element of this requirement is that the bank's s risk-based set of internal policies, procedures, and controls be “reasonably designed.” For example, if a bank's program testing reveals that a new customer type or new activity is high risk, but the bank does not take any action to revise the design of its risk-based set of internal policies, procedures, and controls and therefore treats the customer or activity as presenting low risk, then its program should not be considered reasonably designed. The Board believes that banks have a better understanding of their customer bases and businesses and are best positioned to identify and evaluate their ML/TF risks. Therefore, under this proposed rule Board-supervised banks will continue to have significant flexibility and discretion in their decisions and determinations related to risk identification and resource allocation. The Board will assess whether: (1) a bank's resource allocation decisions are consistent with a reasonably designed risk assessment processes; and (2) with respect to implementation, specifically, whether the bank knows or should know of resource-related issues involving its risk-based set of internal policies, procedures, and controls that may result in the bank failing to implement its AML/CFT program in all material respects and has failed to address such issues.</P>
                <P>Similarly, the Board expects a bank to be examined for its implementation of the established AML/CFT program in all material respects. Merely designating an individual responsible for establishing and implementing the AML/CFT program and having that individual establish risk-based internal policies, procedures, and controls, an ongoing employee training program, and an independent AML/CFT program testing program, are not sufficient to satisfy the proposed rule's obligations for a bank to have an effective AML/CFT program. Rather, a Board-supervised bank would be examined for the implementation, in all material aspects, of its established AML/CFT program, including the determination that the bank is, in fact, allocating resources commensurate with its established AML/CFT program, which the proposed rule would require to be consistent with its reasonably designed risk assessment processes.</P>
                <HD SOURCE="HD1">IV. Section-by-Section Analysis</HD>
                <P>This section-by-section analysis describes the specific proposed changes to the Board's BSA compliance program rule. Section IV.A addresses the proposed incorporation of CFT into the program rule. Section IV.B discusses the requirements for an “effective” AML/CFT program to comply with the requirements of the proposed rule. Section IV.C explains what it means to “establish” and “maintain” an effective AML/CFT program. Section IV.D describes the components of program establishment, including (1) a risk-based set of internal policies, procedures, and controls (including risk assessment processes); (2) independent program testing; (3) an individual, located in the United States and accessible to FinCEN and the Board, responsible for establishing and maintaining the program, and coordinating and monitoring day-to-day compliance; and (4) ongoing employee training. Section IV.E discusses the requirements that the AML/CFT program be written, accessible, and approved by a bank's Board of Directors, an equivalent governing body within the bank, or appropriate senior management. Section IV.F addresses the Customer Identification Program, Section IV.G addresses the supervision and enforcement section of the proposed rule, and Section IV.H discusses technical changes that the proposal makes to the existing rules to improve clarity and consistency across the program rules.</P>
                <HD SOURCE="HD2">A. Inserting the Term “CFT” Into the Program Rules</HD>
                <P>
                    Section 6101(b)(2)(A) of the AML Act amends 31 U.S.C. 5318(h)(1) to reference “countering the financing of terrorism” 
                    <SU>35</SU>
                    <FTREF/>
                     in addition to “anti-money laundering” when describing the requirement to establish an AML/CFT program. The Board proposes to update the AML/CFT program rule to reflect this new statutory language. For example, the proposed rule would change the title of the Board's program rule from “Bank Secrecy Act compliance” to “Anti-Money Laundering/Countering the Financing of Terrorism Compliance, Supervision, and Enforcement.” Similar changes would apply to the titles of relevant sections and subsections.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         Countering the financing of terrorism (CFT) includes laws, rules, regulations, or other measures intended to detect and disrupt the solicitation, collection, or provision of funds to support terrorist acts or terrorist organizations, or other violent extremist groups.
                    </P>
                </FTNT>
                <P>The inclusion of “CFT” in the BSA compliance program rule would not create new obligations for banks, insofar as the USA PATRIOT Act already requires them to account for risks related to terrorist financing. Accordingly, the Board expects any changes to existing AML/CFT programs from the amendments described in this subsection to be technical and therefore not have any substantive impact on Board-supervised banks' compliance obligations.</P>
                <HD SOURCE="HD2">B. An “Effective” AML/CFT Program</HD>
                <P>
                    In prescribing the minimum standards for an AML/CFT program and in supervising and examining compliance with those standards, the AML Act requires the Secretary and the appropriate Federal functional regulator to take into account that effective AML/CFT programs safeguard national security and help law enforcement prevent the flow of illicit funds in the financial system.
                    <SU>36</SU>
                    <FTREF/>
                     Further, the AML 
                    <PRTPAGE P="42368"/>
                    Act contemplates AML/CFT requirements focusing on achieving effective outcomes rather than dictating the processes used to reach those outcomes, an orientation the Board intends to reflect in the proposed rule. Consistent with the Board's long-standing expectations regarding what effective outcomes entail, the Board believes that, as a practical matter, it is not possible for a bank's AML/CFT program to detect and report all potentially illicit transactions that flow through the institution.
                    <SU>37</SU>
                    <FTREF/>
                     Similarly, a bank's AML/CFT program can be effective without preventing every minor instance of a bank falling prey to illicit finance misuse. Accordingly, the proposed rule would set out that, from a supervisory and enforcement perspective, an AML/CFT program is “effective” and complies with the Board's regulatory requirements promulgated under 12 U.S.C. 1818(s), as applicable, so long as it is established and maintained in accordance with applicable requirements.
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         
                        <E T="03">See</E>
                         31 U.S.C. 5318(h)(2)(B)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         Fed. Fin. Inst. Examination Council, 
                        <E T="03">BSA/AML Assessing Compliance with BSA Regulatory Requirements — Suspicious Activity Reporting, https://bsaaml.ffiec.gov/manual/AssessingComplianceWithBSARegulatoryRequirements/04.</E>
                    </P>
                </FTNT>
                <P>The proposed rule would provide that a Board-supervised bank has an “effective” program if it (1) is established in accordance with the proposed rule's establishment requirements; and (2) is maintained, meaning that a properly established AML/CFT program is implemented in all material respects.</P>
                <P>
                    One of the AML Act's key purposes is to “encourage technological innovation and the adoption of new technology by financial institutions to more effectively counter money laundering and financing of terrorism.” 
                    <SU>38</SU>
                    <FTREF/>
                     Consistent with this purpose, the Board encourages banks to evaluate whether new technology or innovative approaches in other resources might help to combat financial crime more effectively. Innovative approaches could involve machine learning, generative artificial intelligence (GenAI), digital identity, blockchain monitoring and analytics, or application programming interfaces (APIs).
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         William M. (Mac) Thornberry National Defense Authorization Act for Fiscal Year 2021, Pub. L. 116-283, 134 Stat. 4547 at section 6002(3) (Jan. 1, 2021).
                    </P>
                </FTNT>
                <P>
                    The Board recognizes that adopting new technologies for BSA compliance may not be suitable for all banks, particularly smaller ones, and the proposed rule therefore does not reference or require the use of any particular technology. A bank may find it beneficial to consider whether its AML/CFT program appropriately uses the bank's existing resources, including technology and data. However, consistent with longstanding guidance, the Board encourages banks to engage in responsible AML/CFT innovation.
                    <SU>39</SU>
                    <FTREF/>
                     Banks that responsibly incorporate innovative technologies into their AML/CFT programs will not incur on that basis any additional risk of being subject to a significant supervisory action or enforcement action solely based on the use of innovative technologies.
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         Board, FDIC, FinCEN, NCUA, OCC, 
                        <E T="03">Joint Statement on Innovative Efforts to Combat Money Laundering and Terrorist Financing,</E>
                         (Dec. 3, 2018), 
                        <E T="03">https://www.fincen.gov/system/files/2018-12/Joint%20Statement%20on%20Innovation%20Statement%20%28Final%2011-30-18%29_508.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Establishing and Maintaining an AML/CFT Program</HD>
                <P>
                    The requirement that a bank establish and maintain an AML/CFT program is not new, although over time various formulations of this requirement have developed in statutes and regulations.
                    <SU>40</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         For instance, the provision of the BSA which requires financial institutions to have AML/CFT program rules states that “each financial institution shall 
                        <E T="03">establish”</E>
                         (emphasis added) such programs, including certain requirements as specified. 
                        <E T="03">See</E>
                         31 U.S.C. 5318(h)(1). The corresponding Federal statute requiring banks regulated by the Federal banking agencies to have BSA compliance programs states that these banks must “establish and maintain procedures reasonably designed to assure and monitor the compliance” with the requirements of the BSA. 12 U.S.C. 1818(s)(1).
                    </P>
                </FTNT>
                <P>
                    The proposed rule would harmonize and delineate the regulatory requirements that must be met for Board-supervised banks to have an effective AML/CFT program. That is, the proposed rule would create a two-pronged framework under which a Board-supervised bank's AML/CFT program would be deemed to be effective if the bank 
                    <E T="03">establishes</E>
                     and 
                    <E T="03">maintains</E>
                     its program. Under the proposed rule, a Board-supervised bank maintains its properly established AML/CFT program by 
                    <E T="03">implementing</E>
                     it in all material respects.
                </P>
                <HD SOURCE="HD3">1. Establishing Versus Maintaining an AML/CFT Program</HD>
                <P>
                    For a Board-supervised bank to have an effective AML/CFT program, the proposed rule would require a bank to 
                    <E T="03">establish</E>
                     an AML/CFT program and then 
                    <E T="03">maintain</E>
                     the AML/CFT program by implementing, in all material respects, the established AML/CFT program. The proposed rule describes the requirements for an effective AML/CFT program to be 
                    <E T="03">established</E>
                     and 
                    <E T="03">maintained.</E>
                     The AML/CFT program minimum components constituting program establishment, and described in further detail in Section IV.D below, are: (1) a risk-based set of internal policies, procedures, and controls (including risk assessment processes); (2) independent program testing; (3) an individual, located in the United States and accessible to FinCEN and the Board, responsible for establishing and maintaining the program, and coordinating and monitoring day-to-day compliance; and (4) ongoing employee training.
                </P>
                <P>“Establishing” an AML/CFT program involves designing an AML/CFT program that incorporates all of the required components. “Maintaining,” by contrast, addresses whether the bank is implementing that program in practice. The regulation uses the term “implement” to describe this second prong. The distinction between establishing a program and maintaining a program by implementation matters because the proposed rule ties the availability of AML/CFT enforcement and significant supervisory actions based on the program rule for an established bank program to a significant or systemic failure to “implement” the properly established AML/CFT program. The distinction between establishing and “maintaining” an AML/CFT program is intended to make transparent how the individual elements of the proposed rule work together.</P>
                <P>Separating program establishment from program maintenance therefore provides needed clarity regarding whether a supervisory concern relates to deficiencies stemming from the program's design, on the one hand, or failures in the program's operation, on the other. This two-prong framework would help promote consistent articulation of supervisory expectations and prevent conflating criticisms of program design—the remediation of which would likely be different in kind—with criticisms of day-to-day implementation. The proposed distinction does not change the substantive obligations for the bank.</P>
                <P>
                    As noted previously, the Board intends for the requirements of this proposed rule to not be limited to a one-time adoption of the elements required for program establishment, such as a risk-based set of internal policies, procedures, and controls. Rather, the Board intends a bank's establishment of its AML/CFT program to require the bank's risk-based set of internal policies, procedures, and controls—and the risk assessment processes that inform them—to remain current as the bank's risk profile changes. For example, if a Board-supervised bank begins providing 
                    <PRTPAGE P="42369"/>
                    a new product or service—or changes how it provides an existing product or service, such as operating in a new geographic location—under this proposed rule, the bank would need to incorporate its new product or service as part of its risk assessment processes. The proposed rule would require a bank to make a risk determination and, as appropriate, redesign its risk-based set of internal policies, procedures, and controls to account for the risks that it did not previously encounter prior to offering the new product or service, or operating in the new geographic location. Thus, under the proposed rule, even where a bank has previously established an AML/CFT program in accordance with the proposed rule, a failure to update the program to reflect significant changes in the bank's risk profile may result in the program no longer satisfying the proposed rule's requirements regarding establishment.
                </P>
                <HD SOURCE="HD3">2. Implementation of an AML/CFT Program</HD>
                <P>Once a Board-supervised bank has properly “established” an AML/CFT program, the bank must “maintain” the program by implementing it, in all material respects. Minor deficiencies of an AML/CFT program would not necessarily mean that a bank has failed to implement the program.</P>
                <P>
                    Although there are a variety of ways that a bank may not be implementing its program “in all material respects,” in the Board's experience, commonly observed examples may include, but would not be limited to: (1) internal policies, procedures, and controls are not being performed or not being performed on a consistent, regular, and timely basis (
                    <E T="03">e.g.,</E>
                     consistently ignored warnings or red flags that a program was seriously deficient) due to the nature or extent of required resources becoming inadequate; (2) gaps in the risk assessment processes that result in the bank's program internal policies, procedures, and controls missing or inadequately covering higher ML/TF risks (
                    <E T="03">e.g.,</E>
                     systems used to monitor for potentially suspicious activity failing to capture material volumes or types of transactions); or (3) deficiencies or weaknesses in the risk assessment processes that have a material impact on the bank's mitigation of ML/TF risks through its risk-based set of internal policies, procedures, and controls, including due to data-related issues involving relevant processes and systems.
                </P>
                <P>
                    Similarly, the Board expects that a bank could become aware of such implementation-related concerns through a variety of mechanisms, including but not limited to: (1) independent testing of the AML/CFT program; (2) examiner observations, suggestions, or other informal comments about the AML/CFT program; (3) management information systems and related reports or other outputs (
                    <E T="03">e.g.,</E>
                     key performance indicators or key risk indicators, such as monitoring for potentially material backlogs in relevant AML/CFT processes); and (4) issues identified by personnel involved in the operation of the bank's AML/CFT program.
                </P>
                <HD SOURCE="HD2">D. Program Establishment</HD>
                <P>As noted earlier, pursuant to 31 U.S.C. 5318(h), the Board's AML/CFT program requirements for Board-supervised banks currently require certain minimum elements, including: (1) a risk-based set of internal policies, procedures, and controls; (2) an independent audit function to test programs; (3) a designated compliance officer; and (4) an ongoing employee training program. The majority of the proposed rule's AML/CFT program components are substantially similar to the existing regulatory requirements for banks. However, the Board is proposing certain additions and modifications to modernize and strengthen Board-supervised banks' AML/CFT programs to allow them to better mitigate illicit finance risks.</P>
                <HD SOURCE="HD3">1. Internal Policies, Procedures, and Controls</HD>
                <P>
                    Banks are currently required to develop “a system of internal controls to assure ongoing compliance” with the requirements of the BSA as part of their AML/CFT programs.
                    <SU>41</SU>
                    <FTREF/>
                     Existing program rules, however, do not clearly articulate what it means to establish such a system of internal policies, procedures, and controls to ensure compliance.
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         
                        <E T="03">See,</E>
                         12 CFR 21.21(d)(1); 12 CFR 208.63(c)(1); 12 CFR 326.8(c)(1); 12 CFR 748.2(c)(1).
                    </P>
                </FTNT>
                <P>Under the proposal, the Board is amending and clarifying the current internal control pillar requirements. Specifically, the proposal provides that Board-supervised banks must establish a risk-based set of internal policies, procedures, and controls that is reasonably designed to: (1) identify, assess, and document ML/TF risks through risk assessment processes; (2) mitigate ML/TF risks consistent with the risk assessment processes, including by directing more attention and resources toward higher-risk customers and activities rather than toward lower-risk customers and activities; and (3) conduct ongoing CDD. The preamble addresses each of these features below.</P>
                <P>Under this proposal, a Board-supervised bank's risk-based set of internal policies, procedures, and controls should be based upon, informed by, and consistent with a bank's risk assessment processes. The internal policies, procedures, and controls should be commensurate with the size, structure, risk profile, and complexity of the bank. The requirement that a bank's risk-based set of internal policies, procedures, and controls be “reasonably designed” gives banks flexibility in how they achieve compliance with the BSA and the proposed rule's other requirements. As part of having a risk-based set of internal policies, procedures, and controls, reasonably designed to ensure compliance, banks may choose to responsibly adopt new technologies or innovative approaches to comply with BSA requirements. Consistent with this purpose, the Board encourages banks to evaluate whether new technology or innovative approaches in other resources might help to more effectively combat financial crime. Innovative approaches could involve machine learning, GenAI, digital identity, blockchain monitoring and analytics, or APIs.</P>
                <HD SOURCE="HD3">i. Risk Assessment Processes</HD>
                <P>The Board is proposing that, as part of a Board-supervised bank's risk-based set of internal policies, procedures, and controls, the bank identify, assess, and document the bank's ML/TF risk through risk assessment processes that: (1) evaluate the ML/TF risks of the bank's business activities, including products, services, distribution channels, customers, and geographic locations; (2) review and, as appropriate, incorporate the AML/CFT Priorities; and (3) update promptly upon any change that the bank knows or has reason to know significantly changes the bank's ML/TF risks.</P>
                <P>
                    The Board has traditionally viewed risk assessment processes as a critical tool of a reasonably designed BSA compliance program; a bank cannot implement a reasonably designed program to achieve compliance with the BSA unless it understands its risk profile.
                    <SU>42</SU>
                    <FTREF/>
                     Most banks already use risk 
                    <PRTPAGE P="42370"/>
                    assessments or risk assessment processes to structure their risk-based compliance programs. Despite being viewed as a critical tool, the Board's regulation does not currently explicitly require such risk assessment processes nor outline mandatory considerations for such processes. Thus, the proposed rule would codify into regulation the requirement for Board-supervised banks to establish risk assessment processes, thereby clarifying existing expectations and practices, as well as require specific factors for consideration that are responsive to the AML Act.
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         Joint Statement on Risk-Focused Bank Secrecy Act/Anti-Money Laundering Supervision (July 22, 2019), 
                        <E T="03">https://www.fdic.gov/sites/default/files/2024-03/pr19065a.pdf.</E>
                         The Joint Statement on Risk Focused BSA/AML Supervision, July 22, 2019, clarifies that the Board and the Agencies' long-standing supervisory approach to examining for compliance with the BSA considers a financial institution's risk profile and notes that “[a] risk-based [AML] compliance program enables a bank to allocate compliance resources commensurate with 
                        <PRTPAGE/>
                        its risk.” It further clarifies that a well-developed risk assessment process assists examiners in understanding a bank's risk profile and evaluating the adequacy of its AML program. The statement also explains that, as part of their risk-focused approach, examiners review a bank's risk management practices to evaluate whether a bank has developed and implemented a reasonable and effective process to identify, measure, monitor, and control risks.
                    </P>
                </FTNT>
                <P>Importantly, the proposed rule requires, as a part of a Board-supervised bank's risk-based set of internal policies, procedures and controls, that it identify, assess, and document its ML/TF risks using risk assessment processes. A bank would retain flexibility in how it would document the results of its risk assessment processes. As proposed, Board-supervised banks would not be required to establish a single, consolidated risk assessment document solely to comply with the proposed rule. While such a document may be appropriate under the proposal, the use of the term “risk assessment processes” is intended to reflect that a financial institution may rely on multiple processes—applied as appropriate within its AML/CFT program—to identify, assess, and document its ML/TF risks and will be examined based on the totality of these processes rather than the sufficiency of a single, standalone risk assessment document.</P>
                <P>The Board believes banks are best positioned to identify and evaluate their ML/TF risk and is therefore not prescribing any particular risk assessment processes or methodologies other than the critical elements described in this proposed rule. Under the proposed rule, Board-supervised banks would be examined for whether they have established and maintained, in all material respects, reasonably designed risk assessment processes—which need not be in the form of a singular risk assessment process. Furthermore, the Board is not prescribing any particular time frame for banks to update their risk assessment processes.</P>
                <P>The Board recognizes that banks vary significantly in size, structure, complexity, and risk profile. Under the proposed rule, a bank's risk-based set of internal policies, procedures, and controls—including its risk assessment processes—should be commensurate with the bank's size, structure, risk profile, and complexity. Accordingly, banks with broader product offerings, more complex corporate structures, or greater exposure to higher-risk customers, products, services, or geographic locations would be expected to establish correspondingly more formalized or analytically complex internal policies, procedures, and controls—including risk assessment processes. By contrast, many community banks operate with more limited business activities, traditional lending and deposit services, a narrower geographic footprint, and customer bases concentrated within defined local communities. For such banks, risk assessment processes may appropriately be more streamlined or qualitative in nature, and a risk-based set of internal policies, procedures, and controls that is reasonably designed for a large, complex financial organization would not necessarily be required or appropriate for a community bank with a more limited risk profile.</P>
                <P>As noted previously, most banks already design their BSA compliance programs based on their assessment of ML/TF risks under existing risk assessment processes. The Board expects that most banks will be able to leverage their existing risk assessment processes to satisfy the proposed requirement without making significant changes.</P>
                <HD SOURCE="HD3">a. ML/TF Risks</HD>
                <P>The proposed rule would require Board-supervised banks' risk assessment processes to evaluate the ML/TF risks of the bank's business activities, including products, services, distribution channels, customers, and geographic locations. These factors are generally well known and often incorporated into current risk assessment processes of banks. While most banks are generally familiar with these concepts, “distribution channels” may be a newer term for some banks. For purposes of this rule, the Board considers “distribution channels” to refer to the methods and tools through which a bank opens accounts and provides products or services, including, for example, through remote or other non-face-to-face means.</P>
                <P>
                    Banks may use a variety of sources to inform their risk assessment processes. Such sources may include information obtained from other financial institutions, such as emerging risks and typologies identified through section 314(b) information sharing or payment transactions that other financial institutions returned or flagged due to ML/TF risks.
                    <SU>43</SU>
                    <FTREF/>
                     Information a bank generates or maintains could be another source. Internal information may include, for example, customer internet protocol (IP) addresses or device logins and related geolocation information.
                </P>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         See FinCEN, 
                        <E T="03">Section 314(b) Fact Sheet,</E>
                         (Dec. 2020), 
                        <E T="03">www.fincen.gov/system/files/shared/314bfactsheet.pdf.</E>
                    </P>
                </FTNT>
                <P>Feedback from FinCEN, law enforcement, and financial regulators may also inform risk assessment processes. For example, if a bank receives feedback from law enforcement about a report it has filed or potential risks at the bank, the bank may incorporate that information into its risk assessment processes. Similarly, banks may consider information identified from responding to section 314(a) requests.</P>
                <P>
                    In addition to feedback, reports and analyses published by Treasury and FinCEN may be particularly relevant to a bank's business activities, thereby warranting consideration when evaluating ML/TF risks. For example, Treasury describes changes in the illicit finance risk environment in its biennial 
                    <E T="03">National Money Laundering Risk Assessment, National Terrorist Financing Risk Assessment,</E>
                     and 
                    <E T="03">National Proliferation Financing Risk Assessment,</E>
                     which highlight significant illicit finance threats, vulnerabilities, and risks.
                    <SU>44</SU>
                    <FTREF/>
                     Regardless of the source, banks should take measures in their risk assessment processes to ensure this information is reasonably current, complete, and accurate.
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         
                        <E T="03">See</E>
                         U.S. Dep't of Treasury, 2026 Nat. Money Laundering Risk Assess. (Mar. 2026), 
                        <E T="03">https://home.treasury.gov/system/files/246/2026-NMLRA.pdf;</E>
                         U.S. Dep't of Treasury, 2026 Nat. Terrorist Financing Risk Assess. (Mar. 2026), 
                        <E T="03">https://home.treasury.gov/system/files/246/2026-NTFRA.pdf;</E>
                         U.S. Dep't of Treasury, 2026 Nat. Proliferation Financing Risk Assess. (Mar. 2026), 
                        <E T="03">https://home.treasury.gov/system/files/246/2026-NPFRA.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">b. AML/CFT Priorities</HD>
                <P>
                    The AML/CFT Priorities set out the priorities for the U.S. government's AML/CFT policy as required by the AML Act and are designed to ensure that banks' AML/CFT programs are aligned with those priorities. Recognizing the diverse nature of ML/TF threats facing the U.S. financial system and national security, and that bank AML/CFT programs benefit U.S. national security by safeguarding the financial system from ML/TF risk, the AML/CFT Priorities are intended to ensure that banks are focusing on the 
                    <PRTPAGE P="42371"/>
                    greatest threats to U.S. national security, as defined by Treasury.
                </P>
                <P>
                    Section 6101 of the AML Act requires that a financial institution's review and appropriate incorporation of the AML/CFT Priorities into its AML/CFT program be subject to supervision and examination for compliance with the BSA and other AML/CFT laws and regulations.
                    <SU>45</SU>
                    <FTREF/>
                     The Board is implementing this statutory requirement by proposing that, as part of their risk assessment processes, Board-supervised banks must review and, as appropriate, incorporate the AML/CFT Priorities. The inclusion of the AML/CFT Priorities in risk assessment processes is meant to help ensure that banks understand their exposure to risks in areas that are of particular importance nationally, which may help banks develop risk-based and reasonably designed AML/CFT programs.
                </P>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         31 U.S.C. 5318(h)(4)(E).
                    </P>
                </FTNT>
                <P>The Board understands that the AML/CFT Priorities may not always be applicable to a bank's risk profile and activities. Therefore, the Board requires the incorporation of the AML/CFT Priorities in a bank's risk assessment processes, as appropriate. This means that, having reviewed the AML/CFT Priorities, a Board-supervised bank may determine the extent to which a particular Priority is applicable and whether and how a particular AML/CFT Priority should be appropriately incorporated into its risk assessment processes.</P>
                <P>
                    Further, a Board-supervised bank may use its judgment and apply a reasonable, risk-based determination on whether to focus on a specific aspect of an AML/CFT Priority, rather than addressing all aspects of a Priority that may either not be applicable or pose lower risks to the bank. However, the Board cautions that a surface-level, perfunctory review of an AML/CFT Priority by a bank and of the foreseeable ways in which it may manifest itself within the bank's customers, products and services, geographies, and distribution channels would not satisfy this requirement. For example, patterns of transactions that may be consistent with potential structuring should not automatically be dismissed as lower value to law enforcement and untethered to an AML/CFT Priority without determining whether there is a potential connection to various types of other illicit finance activity (
                    <E T="03">e.g.,</E>
                     structuring or similar patterns involving transactions in narcotics trafficking proceeds).
                </P>
                <P>Whenever the AML/CFT Priorities are updated, banks would no longer be required to incorporate prior versions of the AML/CFT Priorities. Banks would only be required, as appropriate, to incorporate the most recent AML/CFT Priorities into their risk-based AML/CFT programs.</P>
                <P>
                    The Board anticipates that some Board-supervised banks, such as community banks, may ultimately determine that their business models and risk profiles have limited exposure to some of the threats addressed in the AML/CFT Priorities but instead have greater exposure to other ML/TF risks. Additionally, some banks' risk assessment processes may determine that their AML/CFT programs already sufficiently incorporate to some extent, the AML/CFT Priorities. In either case, any changes to banks' AML/CFT program, such as internal policies, procedures, or controls would be based on the results of risk assessment processes and their impact on the AML/CFT program, including how to review and, as appropriate, incorporate the AML/CFT Priorities before making these determinations.
                    <SU>46</SU>
                    <FTREF/>
                     The Board requests comment from the public on whether additional guidance related to the consideration of the AML/CFT Priorities as part of a Board-supervised bank's risk assessment processes would be warranted.
                </P>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         FinCEN's April 10, 2026, proposal provides additional clarity on how FinCEN anticipates addressing the AML/CFT Priorities. 
                        <E T="03">See</E>
                         91 FR 18704 (Apr.10, 2026).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">c. Updates to Risk Assessment Processes</HD>
                <P>The proposed rule would require Board-supervised banks to update their risk assessment processes promptly upon any change that the bank would know or have reason to know would significantly change their ML/TF risk profile. For example, a bank may need to update its risk assessment when new products, services, and customer types are introduced; existing products, services, and customer types undergo significant changes; when the bank adopts new risk mitigation technology; or the bank as a whole expands or contracts through mergers, acquisitions, and divestitures. Banks may also need to update their risk assessment processes based on factors external to their operations that they know or have reason to know significantly change their ML/TF risk profiles. The Board welcomes comments on whether it should further clarify when Board-supervised banks must review or update their risk assessment processes.</P>
                <HD SOURCE="HD3">ii. Mitigate ML/TF Risks Through Risk-Based Allocation of Attention and Resources</HD>
                <P>
                    Section 6101(b) of the AML Act states that the AML/CFT programs of financial institutions should be “risk-based, including ensuring that more attention and resources of financial institutions should be directed toward higher-risk customers and activities, consistent with the risk profile of a financial institution, rather than toward lower-risk customers and activities.” 
                    <SU>47</SU>
                    <FTREF/>
                     The proposed rule would adopt this formulation as part of a bank's obligation to establish a risk-based set of internal policies, procedures, and controls. Under the proposed rule, a Board-supervised bank's efforts to mitigate its ML/TF risks would involve “directing more attention and resources toward higher-risk customers and activities, consistent with the risk profile of [a bank], rather than toward lower-risk customers and activities.”
                </P>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         31 U.S.C. 5318(h)(2)(B)(iv)(II).
                    </P>
                </FTNT>
                <P>The Board views risk-based allocation of resources as a critical step in realizing the AML Act's BSA modernization and reform ambitions, and consistent with the Board's and the Agencies' ongoing efforts to modernize AML/CFT compliance and supervision. The proposed rule envisions Board-supervised banks exercising more flexibility in deploying attention and resources in accordance with the proposed rule without fear of supervisory criticism or action from examiners for directing more attention and resources on higher risk customers and activities, rather than toward lower risk customers and activities.</P>
                <P>The goal of risk-based resource allocation is for banks to spend less time, energy, and resources on lower priority activities that may result in less resources devoted to and potentially distract from more serious threats. The proposed rule would enable Board-supervised banks to focus more on higher risk customers and activities, which the Board has determined should result in banks being more effective at detecting, reporting, and preventing the flow of illicit funds and providing law enforcement with more valuable BSA reporting.</P>
                <P>
                    As noted above, the Board believes that banks are best positioned to identify and evaluate their ML/TF risk and to make decisions related to risk identification and resource allocation in accordance with risk identification. The proposed rule, therefore, does not contemplate second-guessing of a bank's reasonable determinations regarding 
                    <PRTPAGE P="42372"/>
                    appropriate resource allocation or conclusions regarding specific risks. However, while the Board does not believe that an examiner should substitute his or her own subjective judgment in place of the bank's, examiners will be expected to assess whether (1) a bank's resource allocation decisions are informed by, and consistent with, reasonably designed risk assessment processes; and (2) with respect to implementation, specifically, whether the bank knows or should know of resource-related issues involving its internal policies, procedures, and controls and other mandatory elements that may result in the bank failing to implement its AML/CFT program in all material respects and has failed to address such issues.
                </P>
                <HD SOURCE="HD3">iii. Conduct Ongoing Customer Due Diligence</HD>
                <P>
                    The proposed rule would add CDD as a required component of the Board's AML/CFT program rule. Appropriate risk-based procedures for conducting ongoing CDD—in the form of understanding the nature and purpose of customer relationships and conducting ongoing monitoring—is currently a required component in FinCEN's AML program rule,
                    <SU>48</SU>
                    <FTREF/>
                     and, therefore, banks are already required to comply with these ongoing CDD requirements under FinCEN's rule. The inclusion of risk-based procedures for conducting ongoing CDD in the Board's proposed rule would mirror FinCEN's existing rule and reflect the Board's long-standing supervisory expectations. Long before FinCEN amended its AML program rule to expressly include the CDD component requirement, the Board had considered CDD an integral component of a risk-based program, enabling the bank to understand its customers and its customers' activity to better identify suspicious activity. Adding the CDD component to the Board's AML/CFT program rule will eliminate confusion for Board-supervised banks concerning the current differences with FinCEN's rule. Because banks must already comply with FinCEN's CDD component requirement, the proposed change should not alter current compliance practices.
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         
                        <E T="03">See</E>
                         31 CFR 1020.210(a)(2)(v) and (b)(2)(v).
                    </P>
                </FTNT>
                <P>The proposed rule would incorporate CDD requirements not as a standalone pillar, but instead by making them part of the requirement that banks establish a risk-based and reasonably designed set of internal policies, procedures, and controls. As noted previously, the activities required to conduct ongoing CDD, such as monitoring customer relationships, maintaining and updating customer information on a risk basis, and identifying and reporting suspicious transactions are, in practice, subsumed by the obligation for a bank to have a risk-based and reasonably designed set of internal policies, procedures, and controls and have long been viewed by the Board and the Agencies as an integral component of a bank's internal controls. Accordingly, establishing these requirements within this pillar more accurately reflects how banks operationalize ongoing customer due diligence as part of their overall AML programs.</P>
                <HD SOURCE="HD3">2. Independent Testing</HD>
                <P>
                    Since the original adoption of the BSA compliance program rule, the Board and the Agencies have required banks to perform independent testing. The AML Act did not change the BSA's separate requirement that each bank must independently test its AML/CFT program.
                    <SU>49</SU>
                    <FTREF/>
                     The proposed rule therefore retains the existing requirement for Board-supervised banks to establish independent AML/CFT program testing to be conducted by bank personnel or an outside party with minor, non-substantive clarifications that are not intended to change regulatory requirements.
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         31 U.S.C. 5318(h)(1)(D).
                    </P>
                </FTNT>
                <P>The purpose of independent testing is to assess the bank's compliance with AML/CFT statutory and regulatory requirements, relative to its risk profile. The independent AML/CFT program testing should be focused on whether the AML/CFT program is effective, and it should identify issues and areas for remediation accordingly.</P>
                <P>
                    To support the effective implementations of an AML/CFT program, independent testing should be based on objective criteria designed to assess whether a bank has established and implemented an effective AML/CFT program and allocated resources consistent with its risk assessment processes. These criteria should also assess whether related project governance is sufficient to manage risks and apply compensating controls where necessary, particularly in areas where remediation is underway. This evaluation helps to inform the bank's board of directors and senior management of weaknesses or areas in need of enhancement or stronger controls. Typically, this evaluation includes a conclusion about the bank's overall compliance with AML/CFT statutory and regulatory requirements and sufficient information for the reviewer (
                    <E T="03">e.g.,</E>
                     board of directors, senior management, AML/CFT officer, outside auditor, or an examiner) to reach a conclusion about whether the set of internal policies, procedures, and controls is reasonably-designed, and resources are well-allocated consistent with the bank's risk assessment processes.
                </P>
                <P>
                    Additionally, while banks retain some flexibility regarding who conducts the audit or testing, the proposed rule would continue to require that testing be independent. Banks that do not employ outside auditors or consultants or that do not have internal audit departments may comply with this requirement by using internal staff who are not involved in the function being tested. For these banks and banks with other types of arrangements for independent testing, the AML/CFT officer or any party who directly, and in some cases indirectly, reports to the AML/CFT officer, or an equivalent role, would generally not be considered sufficiently independent. Any individual conducting the testing, whether internal or external, would be required to be independent of other parts of the bank's AML/CFT program, including its oversight. For banks that engage outside auditors or consultants, the bank would be required to ensure that the outside parties conducting the independent testing are not involved in functions related to the AML/CFT program at the bank that may present a conflict of interest or lack of independence, such as AML/CFT training or the development or enhancement of internal policies, procedures, and controls. Additionally, for the purposes of the independent testing component, outside parties would not include government agencies, entities, or instrumentalities, such as a bank's Federal or state functional regulators. Banks with less complex operations and lower risk profiles may consider utilizing a shared resource as part of a collaborative arrangement to conduct testing, as long as the testing is independent.
                    <SU>50</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         
                        <E T="03">See</E>
                         Board, FDIC, NCUA, OCC, and FinCEN, 
                        <E T="03">Interagency Statement on Sharing Bank Secrecy Act Resources</E>
                         (Oct. 3, 2018), 
                        <E T="03">https://www.fincen.gov/news/news-releases/interagency-statement-sharing-bank-secrecy-act-resources.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">3. Designate an AML/CFT Officer Located in the United States</HD>
                <HD SOURCE="HD3">i. Duties of the AML/CFT Officer</HD>
                <P>
                    The Board and the Agencies have required banks to “designate an individual or individuals responsible for coordinating and monitoring day-to-day compliance” since the inception of their program requirements. The BSA 
                    <PRTPAGE P="42373"/>
                    separately requires that banks with AML/CFT program obligations must have a designated compliance officer, which was not altered by the AML Act. As in the Board's current BSA compliance program rule, the proposed rule would provide that an AML/CFT program must designate an individual (referred to as an AML/CFT officer) responsible for establishing and implementing the AML/CFT program and coordinating and monitoring day-to-day compliance with the requirements and prohibitions of the BSA and FinCEN's implementing regulations. The Board's view is that the individual serving as the AML/CFT officer must be qualified for that role and not overburdened with other responsibilities at the institution. The Board is proposing clarifying and technical changes to the AML/CFT officer requirement, as well as changes to incorporate to FinCEN's interpretation of 31 U.S.C. 5318(h)(5), as discussed below. These changes are generally not expected to impose new obligations on banks.
                </P>
                <P>Consistent with current requirements, the proposed rule is not intended to be primarily concerned about the formal title of the individual responsible for establishing and implementing the AML/CFT program and coordinating and monitoring day-to-day compliance; instead, the proposed rule focuses on the AML/CFT officer's position in the bank's organizational structure that enables the AML/CFT officer to effectively establish and implement the bank's AML/CFT program. The AML/CFT officer's authority, independence, and access to resources within the bank are critical. An AML/CFT officer should have decision-making capability regarding the AML/CFT program and sufficient functional stature within the organization to ensure that the program meets BSA requirements.</P>
                <P>The AML/CFT officer's access to resources may include: adequate compliance funds and staffing with the skills and expertise appropriate to the bank's risk profile, size, and complexity; an organizational structure that supports compliance and effectiveness; and sufficient technology and systems to support the timely identification, measurement, monitoring, reporting, and management of the bank's ML/TF risks. An AML/CFT officer with conflicting responsibilities that adversely impact the officer's ability to effectively coordinate and monitor day-to-day AML/CFT compliance generally would not fulfill this requirement. The addition of the explicit requirement that the AML/CFT officer be responsible for “establishing and maintaining the AML/CFT program” in the proposed rule would make explicit a long-standing supervisory expectation, rather than changing current supervisory expectations.</P>
                <HD SOURCE="HD3">ii. The AML/CFT Officer Must Be Located in the United States and Accessible to Regulators</HD>
                <P>
                    The AML Act provides that the duty to establish, maintain, and enforce a bank's AML/CFT program shall remain the responsibility of, and be performed by, persons in the United States who are accessible to, and subject to oversight and supervision by, the Secretary and the appropriate Federal functional regulator.
                    <SU>51</SU>
                    <FTREF/>
                     Because this is a new requirement under the AML Act, it is not currently reflected in the Board's program rule requirements. FinCEN's proposed revisions to its AML/CFT program rules interpret this requirement as applying to the AML/CFT officer, so the Board's proposed rule would amend the existing compliance officer requirements to align with FinCEN's proposal.
                    <SU>52</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         31 U.S.C. 5318(h)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         
                        <E T="03">See</E>
                         91 FR 18704 (April 10, 2026).
                    </P>
                </FTNT>
                <P>
                    The Board recognizes banks may currently have AML/CFT staff and operations outside of the United States, or they may contract out or delegate parts of their AML/CFT operations to third-party providers located outside of the United States. These arrangements may serve to improve cost efficiencies; to enhance coordination, particularly with respect to cross-border operations; or serve other purposes not in conflict with goals underlying the BSA. Consequently, under the proposed rule, while the AML/CFT officer must be located in the United States, personnel located outside of the United States would still be permitted to perform certain AML/CFT functions. This language does not alter existing regulations and guidance that generally prohibit the sharing of SARs with personnel located outside of the United States, other than in limited circumstances such as a bank's foreign head office or controlling company.
                    <SU>53</SU>
                    <FTREF/>
                     The Board requests comment on whether any further clarifications on this point would be useful.
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         
                        <E T="03">See, e.g.,</E>
                         FinCEN, 
                        <E T="03">Financial Crimes Enforcement Network; Confidentiality of Suspicious Activity Reports,</E>
                         75 FR 75593 (Dec. 3, 2010); 
                        <E T="03">see also</E>
                         FinCEN, 
                        <E T="03">Interagency Guidance on Sharing Suspicious Activity Reports with Head Offices and Controlling Companies</E>
                         (Jan. 20, 2006), 
                        <E T="03">https://www.fincen.gov/system/files/guidance/sarsharingguidance01122006.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">4. Ongoing Employee Training Program</HD>
                <P>
                    The BSA requires AML/CFT programs to include an “ongoing employee training program.” 
                    <SU>54</SU>
                    <FTREF/>
                     This statutory requirement is reflected in the current Board program rule employing different wording.
                    <SU>55</SU>
                    <FTREF/>
                     The proposed rule would harmonize the Board's program rule with that of other financial regulators by adopting the BSA's “ongoing employee training program” language uniformly.
                    <SU>56</SU>
                    <FTREF/>
                     This change is clarifying, not substantive.
                </P>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         31 U.S.C. 5318(h)(1)(C).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         12 CFR 208.63.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         Other financial regulators with stakeholders subject to the BSA currently utilize their own versions of this requirement. 
                        <E T="03">See</E>
                         31 CFR 1020.210(a)(2)(iv), (b)(2)(iv) (banks); 1021.210(b)(2)(iii) (casinos); 1022.210(d)(3) (MSBs); 1023.210(b)(4) (broker-dealers); 1024.210(b)(4) (mutual funds); 1025.210(b)(3) (insurance companies); 1026.210(b)(4) (FCMs and IBCs); 1027.210(b)(3) (DPMSJs); 1028.210(b)(3) (operators of credit card systems); 1029.210(b)(3) (loan or finance companies); 1030.210(b)(3) (housing GSEs).
                    </P>
                </FTNT>
                <P>The Board would generally expect training to cover a bank's internal policies, procedures, and controls, which should in turn reflect the results of the bank's risk assessment processes, the latest AML/CFT regulatory requirements, and other relevant information. The frequency with which the training would occur, and the content of the training, would depend on the bank's ML/TF risk profile and the roles and responsibilities of the persons receiving the training. The Board welcomes comment on whether any further clarifications of the proposed training requirement are needed and recognizes that banks may have employees and non-employees who may have a variety of roles and responsibilities in relation to the AML/CFT program. The risk-based nature of an AML/CFT program provides flexibility for financial institutions to identify both employees and non-employees who must be trained on an ongoing basis.</P>
                <HD SOURCE="HD2">E. Access to and Approval of a Written AML/CFT Program</HD>
                <HD SOURCE="HD3">1. Written AML/CFT Programs Must Be Made Available Upon Request</HD>
                <P>
                    The Board's current BSA compliance program rule generally requires a Board-supervised bank to have a written AML/CFT program that is approved by the bank's board of directors.
                    <SU>57</SU>
                    <FTREF/>
                     The proposed rule would modify these requirements and move them to a separate subsection and add clarifying text to harmonize the language with FinCEN's proposed rule. The Board requests comment on whether further clarification on this point would be useful.
                </P>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         
                        <E T="03">See</E>
                         12 CFR 208.63(b)(1).
                    </P>
                </FTNT>
                <PRTPAGE P="42374"/>
                <HD SOURCE="HD3">2. Bank Approval of a Written AML/CFT Program</HD>
                <P>Banks subject to Board supervision currently must have board approval for their AML/CFT programs under the Board's rule. The proposed rule would continue to require that a bank's written AML/CFT program be approved, though the proposal will expand the options available for a bank to obtain such approval. Specifically, the proposed rule will require that the AML/CFT program be approved by the bank's board of directors or an equivalent governing body within the bank, or appropriate senior management. The proposed rule specifies that approval encompasses each of the components of the AML/CFT program.</P>
                <P>
                    With respect to the new “equivalent governing body” language, FinCEN's current rule requires a bank lacking a Federal functional regulator to obtain approval of the bank's written AML program from either the bank's board or an equivalent governing body.
                    <SU>58</SU>
                    <FTREF/>
                     The Board `s proposed rule would also add a reference to an “equivalent governing body” to clarify that a bank can satisfy the requirement by having an equivalent governing body approve the program. The equivalent governing body can take different forms. For example, for the U.S. branch of a foreign bank, the equivalent governing body may be the foreign banking organization's board of directors or delegates acting under the board's express authority. Similarly, banks that do have a board of directors might instead reasonably delegate the approval requirement to a board committee exercising targeted oversight, such as a compliance committee, which would similarly qualify as an “equivalent governing body” under the proposal.
                </P>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         
                        <E T="03">See</E>
                         12 CFR 1020.210(b)(3).
                    </P>
                </FTNT>
                <P>Finally, the rule would also permit a bank's senior management to approve the AML/CFT program. Such individuals may include Chief Executive Officer, Chief Financial Officer, Chief Operations Officer, Chief Legal Officer, Chief Compliance Officer, Director, and individuals with similar status or functions. Also, banks may establish or utilize existing senior committees of appropriate senior management officials to perform these functions. The Board proposes permitting approval by senior management to reflect the division of roles and responsibilities between a bank's board of directors and senior management with respect to establishing and maintaining an AML/CFT program, as a bank's senior management is charged with the actual role of establishing and maintaining the AML/CFT program.</P>
                <P>While the proposed rule will no longer require the bank's board to approve the AML/CFT program, this would not alter the Board's expectations regarding the responsibilities of a bank's board of directors for providing appropriate oversight of the bank's AML/CFT compliance. The Board has always expected bank boards, both as a whole or through appropriate committees, to provide appropriate oversight of senior management to maintain the bank's operations in a safe and sound manner, oversee compliance with applicable laws and regulations, and establish appropriate risk governance frameworks. A bank's board might reasonably permit appropriate senior management to have AML/CFT program approval authority to provide more effective, timely oversight on a day-to-day basis, while still fulfilling the board's obligations through other appropriate means.</P>
                <HD SOURCE="HD2">F. Customer Identification Program</HD>
                <P>The proposed rule would maintain the current Customer Identification Program requirements but would move them to a separate section. The Board proposes minor, non-substantive updates to reference the “AML/CFT” terminology and harmonize the language between the Board and the Agencies to “require a customer identification program to be implemented as part of the AML/CFT program.” These technical changes are not anticipated to establish new obligations.</P>
                <HD SOURCE="HD2">G. Supervision and Enforcement</HD>
                <P>The proposed rule would add new supervision and enforcement frameworks for banks' AML/CFT programs that are aligned with the AML Act's emphasis on effectiveness and risk-based supervision. The proposed rule defines key terms and describes the Board's enforcement and supervision policy with respect to AML/CFT program implementation failures. The enforcement requirements only apply to actions by the Board.</P>
                <HD SOURCE="HD3">1. Definitions</HD>
                <P>Proposed section (a) would define several terms used throughout the section. The term “AML/CFT requirement” would mean a requirement of the Bank Secrecy Act (as that term is defined in 31 CFR 1010.100) or of the regulations in title 31, chapter X, or a requirement prescribed under the proposed definition.</P>
                <P>The term “AML/CFT enforcement action” would mean any formal or informal action taken by the Board under authority of 12 U.S.C. 1818 or other applicable law that seeks to penalize, remedy, prevent, or respond to noncompliance with past or ongoing violations of, or past or ongoing deficiencies relating to, an AML/CFT requirement. The term includes a cease-and-desist order, written agreement, consent order, or memorandum of understanding, or the assessment of a civil money penalty.</P>
                <P>The term “significant AML/CFT supervisory action” would mean any written communication or other formal supervisory determination issued by the Board that identifies one or more alleged deficiencies, weaknesses, violations of law, or unsafe or unsound practices or conditions relating to an AML/CFT requirement; communicates supervisory expectations to a bank regarding actions or remedial measures required to correct the deficiency, weakness, violation, or practice or condition; and contemplates significant or programmatic actions or remedial measures to be taken by the bank. The term does not include examiner observations, suggestions, or other informal comments.</P>
                <HD SOURCE="HD3">2. Enforcement and Supervision Policy</HD>
                <P>
                    The proposed rule would articulate the Board's enforcement and supervision policy as it relates to AML/CFT requirements.
                    <SU>59</SU>
                    <FTREF/>
                     Except with respect to a significant or systemic failure to implement in all material respects an established AML/CFT program in accordance with the proposed rule, a Board-supervised bank that has properly established an AML/CFT program would not be subject to an AML/CFT enforcement action or to a significant AML/CFT supervisory action based on the program rule. At the same time, the proposed rule would clarify that nothing in this policy would restrict an AML/CFT enforcement action or a significant AML/CFT supervisory action with respect to a failure to 
                    <E T="03">establish</E>
                     an AML/CFT program. The proposal is only intended to affect actions by the Board.
                </P>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         The proposal would not be intended to affect or restrict criminal enforcement under the BSA or the authority of the Department of Justice to pursue such actions.
                    </P>
                </FTNT>
                <P>
                    In addition to these policies, the Agencies' April 10, 2026, proposed rules include two provisions regarding consultation and information sharing with FinCEN.
                    <SU>60</SU>
                    <FTREF/>
                     The first provision 
                    <PRTPAGE P="42375"/>
                    would establish a FinCEN notice and consultation framework applicable when the Agencies intend to initiate an AML/CFT enforcement action or a significant AML/CFT supervisory action. The second provision would allow banks to share any information with the FinCEN Director that relates to an existing or potential AML/CFT enforcement action or significant AML/CFT supervisory action. The Board invites comment on whether it should consider including the same or similar provisions in its final rule, including with respect to the two options for sharing information outlined in the Agencies' proposals.
                </P>
                <FTNT>
                    <P>
                        <SU>60</SU>
                         The two provisions are proposed 12 CFR 21.21(h) and (i) (OCC), 12 CFR 326.8(h) and (i) 
                        <PRTPAGE/>
                        (FDIC), and 12 CFR 748.2(h) and (i) (NCUA). 
                        <E T="03">See</E>
                         91 FR 18304 (Apr. 10, 2026).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">H. Other Changes for Modernization, Clarification, and Consistency</HD>
                <P>In addition to the previously described changes, the proposed rule would make other revisions to increase clarity and consistency in the program rules. Most of these changes are technical, such as renumbering provisions, amending cross-references, and updating statutory references based on changes to the BSA by the AML Act. For example, along with FinCEN, references to “BSA/AML programs” are being updated to “AML/CFT programs” for financial institutions. This technical change is not anticipated to establish new obligations.</P>
                <HD SOURCE="HD1">V. Severability</HD>
                <P>The Board proposes that if one portion of the proposed rule, if finalized, is found to be invalid, the invalidated portion of the regulation should be severed with the other portions of the proposed rule remaining in full force and effect. The Board's position is that invalidation of any one provision, or application thereof to any one person or circumstance, does not, and should not, affect any other provision in this proposed regulation or other existing regulations. Each provision serves an important, related, but distinct purpose and application, designed to benefit the public by protecting the U.S. financial system from illicit financial activity. The Board accordingly proposes incorporating this into its rules, such that invalidating one provision would not undermine the operability or usefulness of the other provisions.</P>
                <HD SOURCE="HD1">VI. Final Rule Effective Date</HD>
                <P>The Board is proposing an effective date of 12 months from the date of issuance of the final rule to allow sufficient time for banks to review and implement the requirements of the proposed rule. The Board solicits comment on the proposed effective date.</P>
                <HD SOURCE="HD1">VII. Request for Comment</HD>
                <P>The Board welcomes comment on all aspects of the proposed amendments but specifically seeks comment on the questions below. The Board encourages commenters to reference specific question numbers when responding.</P>
                <HD SOURCE="HD2">An “Effective” AML/CFT Program (IV.B)</HD>
                <P>1. The proposed rule sets forth the conditions for an effective AML/CFT program. Is the description of an effective program sufficiently clear or is there anything further that the Board should consider in the final rule adding to clarify program effectiveness?</P>
                <P>2. The proposed rule reflects a determination by the Board that banks are best placed to identify risks and allocate resources, and that providing them with greater discretion in these areas will improve the quality of AML/CFT compliance and reporting to law enforcement. Is this correct or should the Board consider adding more requirements regarding allocation of resources? How might banks assess changes in the total allocation of resources devoted to an AML/CFT program in a changing risk and cost environment?</P>
                <HD SOURCE="HD2">Establishing and Maintaining an AML/CFT Program (IV.C)</HD>
                <P>3. Do banks distinguish between establishing a program and maintaining a program by implementing the program? If so, how? Should the Board add anything to further define these terms in the final rule?</P>
                <P>4. Should the proposed rule's distinction between “establishing” and “maintaining” a program be modified? Is the distinction between “establishing” and “maintaining” a compliance program useful for banks?</P>
                <P>5. Should the proposed rule distinguish between “establishing” and “maintaining” at the program level and “establishing” and “maintaining” each individual element? For example, should the final rule more clearly differentiate between a failure to establish the program, as a whole, versus a failure to establish an individual mandatory component of the program?</P>
                <P>6. Is clarification needed for banks to determine what constitutes a “significant or systemic failure” to implement in all material respects a properly established AML/CFT program?</P>
                <P>7. Is clarification needed for banks to determine what constitutes a “failure to establish an AML/CFT program”?</P>
                <P>8. How should the proposed rule ensure that the regulations issued by FinCEN, the Board, and the Agencies function harmoniously? How should the proposed rule differentiate between the Secretary of the Treasury's responsibility for regulations on establishing AML/CFT programs and the Board's responsibilities for regulations on establishing and maintaining programs?</P>
                <HD SOURCE="HD2">Internal Policies, Procedures, and Controls (IV.D.1)</HD>
                <P>9. Do banks expect any changes to their existing internal policies, procedures, and controls under the proposed rule, which requires that internal policies, procedures, and controls be “risk-based” and “reasonably designed” to ensure compliance with the BSA?</P>
                <HD SOURCE="HD2">Risk Assessment Processes (Generally) (IV.D.1.i)</HD>
                <P>
                    10. The proposed rule refers to risk assessment 
                    <E T="03">processes</E>
                     rather than a risk assessment 
                    <E T="03">process.</E>
                     This leaves banks free to use findings from one or more processes to assess their ML/TF risk. Does this description of how banks assess their ML/TF risk provide sufficient flexibility? How should the Board describe “risk assessment processes” to better reflect how banks assess ML/TF risks?
                </P>
                <P>11. Should risk assessment processes be required to take into account additional or different criteria or risks than those listed in the proposed rule? If so, what additional factors should the Board consider requiring?</P>
                <P>12. How long does it generally take a bank to incorporate the results of a risk assessment into its AML/CFT program? What factors determine this time frame?</P>
                <HD SOURCE="HD2">Risk Assessment Processes (AML/CFT Priorities) (IV.D.1.i.b)</HD>
                <P>13. What, if any, difficulties do banks anticipate when incorporating the AML/CFT Priorities as part of their risk assessment processes?</P>
                <P>14. What additional guidance on how to incorporate the AML/CFT Priorities into a bank's risk assessment processes would be useful for the Board to provide?</P>
                <HD SOURCE="HD2">Risk Assessment Processes (Updates) (IV.D.1.i.c)</HD>
                <P>
                    15. The proposed rule requires that risk assessment processes are updated promptly upon any change that the bank knows or has reason to know significantly changes the bank's money 
                    <PRTPAGE P="42376"/>
                    laundering, terrorist financing, and other illicit finance activity risks. Would the proposed update requirement change the way banks currently update their risk assessment processes, and if so how? Is additional explanation needed concerning when a financial institution would be required to update its risk assessment? In particular, how might the Board clarify how risk assessment processes would be updated “promptly”? Would an alternative approach, such as periodic updates or a set schedule for updates, be preferable? Would an alternative standard, such as “materially changes,” be clearer than “significantly changes”?
                </P>
                <P>16. How do a bank's ML/TF risks and its risk assessment processes affect one another? Put differently, if there is a feedback loop between the two, please describe it, including the typical amount of time between discovering new risks and incorporating those findings into risk assessment processes.</P>
                <HD SOURCE="HD2">Independent AML/CFT Program Testing To Be Conducted by Bank Personnel or by an Outside Party (IV.D.2)</HD>
                <P>
                    17. Under the proposed rule, a bank is required to conduct independent AML/CFT program testing. This requirement is already reflected in existing AML program rule requirements as is the requirement to include “an independent audit function to test programs.” 
                    <SU>61</SU>
                    <FTREF/>
                     The Board solicits comment on how financial institutions may interpret and carry out this requirement, based on the proposed rule's description of an effective AML/CFT program. Are further clarifications on the independent AML/CFT program testing requirement necessary to ensure that audits carried out by bank personnel or outside third parties are well-tailored, risk-based, and focused on effectiveness?
                </P>
                <FTNT>
                    <P>
                        <SU>61</SU>
                         12 CFR 21.21(d)(2); 12 CFR 208.63(c)(2); 12 CFR 326.8(c)(2); 12 CFR 748.2(c)(2).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">AML/CFT Officer Located in the United States (IV.D.3.ii)</HD>
                <P>18. Under the proposed rule, while the AML/CFT officer must be located in the United States, personnel located outside of the United States would still be permitted to perform certain AML/CFT functions. This language does not alter existing regulations and guidance that generally prohibit the sharing of SARs with personnel located outside of the United States other than limited circumstances such as a bank's foreign head office or controlling company. Are any further clarifications on this issue needed?</P>
                <HD SOURCE="HD2">Written AML/CFT Program and Approval (IV.E)</HD>
                <P>
                    19. The proposed rule standardizes the long-standing requirement that an AML/CFT program be written. Should the Board further clarify which specific elements of an institution's AML/CFT program must be written, or is this requirement generally understood in its current form? In particular: (a) which program components—such as risk assessment processes; internal policies, procedures, and controls; transaction monitoring rules and parameters; escalation and reporting protocols; independent testing results; training materials; and documentation of designated personnel—should be required in writing; (b) what form (
                    <E T="03">e.g.,</E>
                     narrative descriptions, checklists, system configurations, or electronic records) such documentation should take; and (c) what level of detail is appropriate for each component? Should the Board instead alter the requirement that an AML/CFT program be expressly required to be “written”? What would be the benefits or drawbacks of any such alterations to this requirement?
                </P>
                <P>
                    20. The proposed rule would require that a bank's written AML/CFT program be approved by its board of directors, an equivalent governing body within the bank, or appropriate senior management. Should the Board further clarify which aspects of the AML/CFT program must be subject to such approval? In particular: (a) should approval be required for each of the core program components (
                    <E T="03">e.g.,</E>
                     the risk assessment processes framework; internal policies, procedures, and controls; transaction-monitoring and escalation frameworks; independent testing structure; training program; and designation of responsible personnel), or would approval of the overall program framework be sufficient; (b) should material revisions to particular components (such as significant changes to the institution's risk assessment methodology, monitoring architecture, or governance structure) require re-approval at the same level; and, (c) what level of specificity should the approving body be required to review and approve (
                    <E T="03">e.g.,</E>
                     high-level program architecture versus detailed procedures or parameter-level settings)? Should the Board instead eliminate the specified approval requirement, allowing banks flexibility in determining how leadership oversight of the AML/CFT program is structured? What would be the benefits or drawbacks of not prescribing a mandatory approval requirement in the regulation? If the Board does not eliminate the specified approval requirement, should the Board consider amending the requirement? Are there alternatives to board of directors or an equivalent governing body, such as “appropriate senior management” that would be more appropriate?
                </P>
                <HD SOURCE="HD2">Supervision and Enforcement (IV.G)</HD>
                <P>21. Is clarification needed for banks to determine what constitutes a “significant or systemic failure” to implement an established AML/CFT program?</P>
                <P>22. Is clarification needed for banks to determine what constitutes a “failure to establish an AML/CFT program”?</P>
                <P>23. The Agencies included two provisions in their proposed rules that are not included in the Board's proposed rule regarding consultation and information sharing with FinCEN. Should the Board include the same or similar provisions in its rule?</P>
                <P>24. The definition of significant AML/CFT supervisory action includes the term “any written communication.” Is the term “any written communication” too broad? Are there downsides and negative consequences to including the term “any written communication” in the proposed regulatory text? If so, please describe. Should the term “any written communication” be more clearly defined or removed altogether?</P>
                <P>26. Is the definition of the term “significant AML/CFT supervisory action” sufficiently clear? Does the inclusion of “unsafe or unsound practices or conditions” introduce confusion about what types of supervisory actions are covered, since those terms are not found in the BSA?</P>
                <HD SOURCE="HD2">Other Topics</HD>
                <P>28. Should the rule be revised to tailor program requirements or implementation timelines to the size, complexity, or risk profile of the bank?</P>
                <HD SOURCE="HD2">Final Rule Effective Date (V.)</HD>
                <P>29. The Board is proposing an effective date of 12 months from the date of issuance of the final rule to allow sufficient time for financial institutions to review and implement their requirements. The Board solicits comment on the proposed effective date.</P>
                <HD SOURCE="HD1">VII. Regulatory Impact Analysis</HD>
                <P>
                    The proposed rule, if finalized, would modernize and align the Board's AML/CFT program requirements at 12 CFR part 208 with the rules proposed separately by FinCEN under the BSA, as amended by the AML Act,
                    <SU>62</SU>
                    <FTREF/>
                     and the 
                    <PRTPAGE P="42377"/>
                    Agencies on April 10, 2026.
                    <SU>63</SU>
                    <FTREF/>
                     As described in Sections I-V of this 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                    , the proposed rule would: clarify the elements of an effective, risk-based, and reasonably designed AML/CFT program; codify risk-assessment processes; distinguish program establishment from program implementation; and implement new supervision and enforcement frameworks. As a result of these changes, the Board expects that banks would recalibrate their AML/CFT programs to concentrate on higher-risk activities and deprioritize lower-risk activities, resulting in greater overall efficiency in their AML/CFT programs.
                </P>
                <FTNT>
                    <P>
                        <SU>62</SU>
                         31 U.S.C. 5311-5336.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>63</SU>
                         91 FR 18704 (Apr.10, 2026) and 91 FR 18304 (Apr. 10, 2026).
                    </P>
                </FTNT>
                <P>
                    In accordance with OMB Circular A-4, the Board estimates the annual effect of the proposed rule as the difference in estimated economic outcomes between a state of the world in which the proposed rule is adopted and a baseline state of the world in which the proposed rule is not adopted. This analysis assumes that in both states of the world, all other relevant regulations and financial conditions data for all banks supervised by the Board as of the quarter ending September 30, 2025, with one exception: because the proposed rule is being promulgated in coordination with a rulemaking by FinCEN that will modify rules regarding AML/CFT for a broader set of institutions regulated by FinCEN, the analysis assumes FinCEN's rulemaking is finalized under both the baseline and under the proposed rule. This assumption allows the analysis to focus on the effects specific to the proposed rule. Because all banks are required to comply with the BSA, the proposed rule would apply to 858 banks supervised by the Board.
                    <SU>64</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>64</SU>
                         Call Report data as of September 30, 2025.
                    </P>
                </FTNT>
                <P>Under the baseline, banks must establish and maintain effective AML/CFT programs. These programs must include risk-based internal policies, procedures, and controls; a designated compliance officer; ongoing employee training; and independent testing. Banks also must meet FinCEN's CDD requirements. The analysis below evaluates incremental impacts of the proposal against that baseline.</P>
                <P>
                    Overall, the proposed rule is expected to provide direct benefits to banks through increased clarity of rules and increased consistency of enforcement for banks across financial regulators. The rule also codifies the general practice among banks to calibrate their AML/CFT programs to concentrate on higher-risk activities and deprioritize lower-risk activities. This recalibration would provide indirect benefits including the potential for reductions in crime due to greater deterrence and restriction of the flow of illicit funds as well as potentially increased access to financial services by low-risk members of the public.
                    <SU>65</SU>
                    <FTREF/>
                     The Board expects that the proposed rule would impose relatively small one-time adjustment costs on banks to update their AML/CFT programs to align with the newly-clarified requirements. Compliance costs are not anticipated to increase on an on-going basis, as overall program requirements have been clarified rather than increased and banks already maintain robust AML/CFT programs. The remainder of this section discusses these effects in turn.
                </P>
                <FTNT>
                    <P>
                        <SU>65</SU>
                         For example, there is at least some anecdotal evidence that otherwise normal (low risk) customers could have reduced access as a result of BSA compliance. 
                        <E T="03">See https://www.banking.senate.gov/imo/media/doc/klein_testimony_2-5-25.pdf</E>
                         at 4.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. Benefits</HD>
                <HD SOURCE="HD3">1. Benefit to the Public: Reduction in Money Laundering and Terrorist Financing</HD>
                <P>Effective AML/CFT programs can deter illicit behavior by preventing the flow of illicit funds and assisting law enforcement and national security efforts to identify and prosecute criminals. By clarifying banks' AML/CFT obligations, the proposed rule may improve the effectiveness of AML/CFT programs for banks, relative to the baseline, by enabling them to reallocate AML/CFT resources toward higher-risk customers and activities. This recalibration may reduce the frequency and severity of harm caused by criminal activity.</P>
                <P>
                    Reductions in illicit financial activities from effective AML/CFT programs have several benefits, both for affected banks as well as for the broader society. For banks, effective AML/CFT programs may result in direct cost savings due to a decreased likelihood that they will be subject to illicit schemes, which in turn decreases the probability of disruptions to a bank's normal business operations. It could result in other potential cost savings due to a decreased probability that a bank may need to make victimized customer accounts whole, conduct internal investigations of successful illicit schemes, or implement remediation steps to address and prevent future recurrences of previously successful illicit schemes.
                    <SU>66</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>66</SU>
                         
                        <E T="03">See</E>
                         Citizens Rulemaking Alliance comment letter (Nov. 17, 2025), p. 2, submitted in context of the recent proposed rulemaking 90 FR 48835: Unsafe or Unsound Practices; Matters Requiring Attention. The letter provided conservative estimates for general burden to community banks to address matters sufficiently deficient to warrant a supervisory action of a Matters Requiring Attention. Their provided estimates suggested 120 internal staff hours per MRA to scope, draft, implement, and document a written remediation plan; 20 board/committee hours for oversight and attestation; and $15,000 in external advisory/legal services for complex MRAs. Staff expect that costs would be even greater for larger, more complex banks to remediate significant deficiencies or system failures in their AML/CFT programs.
                    </P>
                </FTNT>
                <P>
                    In terms of broader societal benefits, AML/CFT activities are often tied to other illicit activities such as but not limited to drug, weapons, wildlife, or human trafficking as well as terrorist activities. Any reduction in money laundering or terrorist financing is a benefit to society given the nature of the illegal activities that AML/CFT programs are designed to prevent. While it is inherently difficult to estimate the annual reduction in crime generally or financial crime specifically that could result from more effective AML/CFT programs, recent estimates suggest that those illicit activities run to the billions or trillions of dollars 
                    <SU>67</SU>
                    <FTREF/>
                     and affect millions of Americans,
                    <SU>68</SU>
                    <FTREF/>
                     and given that scale, even a very small percentage decrease would result in a meaningful benefit.
                </P>
                <FTNT>
                    <P>
                        <SU>67</SU>
                         The net annual cost of crime in the U.S. was estimated at approximately $3-4 trillion net of transfers in David A. Anderson, “The Aggregate Cost of Crime in the United States,” 
                        <E T="03">The Journal of Law and Economics,</E>
                         vol 64 no. 4 (2021). One specific type of financial crime, fraud, resulted in over $12 billion in reported losses in 2024 (
                        <E T="03">see</E>
                         the Federal Trade Commission, 
                        <E T="03">Consumer Sentinel Network Data Book 2024</E>
                         (Mar. 2025), 
                        <E T="03">https://www.ftc.gov/system/files/ftc_gov/pdf/csn-annual-data-book-2024.pdf</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>68</SU>
                         There were over 6 million reports according to the Consumer Sentinel Network in 2024 (
                        <E T="03">see</E>
                         Federal Trade Commission, 
                        <E T="03">Consumer Sentinel Network Data Book 2024</E>
                         (Mar. 2025), 
                        <E T="03">https://www.ftc.gov/system/files/ftc_gov/pdf/csn-annual-data-book-2024.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Benefit to the Public: Increased Access to Financial Services</HD>
                <P>An additional benefit of a recalibration of AML/CFT programs towards higher-risk activities under the proposed rule is that fewer low-risk clients or customers, or potential clients and customers, of banks would be inadvertently or accidentally denied access to banking services due to their non-illicit transactions being incorrectly flagged by an AML/CFT program. The Board lacks the data to quantify the scale of this benefit.</P>
                <HD SOURCE="HD3">3. Benefit to Banks: Increased Clarity, Supervisory Coherence, and More Effective AML/CFT Programs</HD>
                <P>
                    The proposed rule would generate additional qualitative benefits from increased clarity and supervisory 
                    <PRTPAGE P="42378"/>
                    coherence, relative to the baseline. These benefits include: reducing regulatory fragmentation by harmonizing the Board and the Agencies' regulations imposing obligations on banks with FinCEN's corresponding regulations and eliminating overlap pertaining to the CDD requirements; enhancing outcomes related to national security and law enforcement by reinforcing risk-based approaches; and enabling more consistent identification and reporting of higher-priority illicit activity.
                </P>
                <P>Having effective AML/CFT programs also reduces a bank's probability of regulatory and legal consequences, which may otherwise increase a bank's costs and adversely affect earnings. For example, ineffective programs that lead to significant AML/CFT activities may result in subsequent higher: operational risk capital requirements for larger banks currently subject to operational risk regulations; compliance costs from increased regulatory monitoring; or legal costs and financial penalties if program deficiencies result in violations of law, such as potential enforcement actions and civil money penalties.</P>
                <P>Although these benefits are not readily quantifiable, they are expected to improve the focus of (1) AML/CFT supervision on mitigating significant or systemic failures in a bank's AML/CFT program and (2) bank compliance programs on higher-risk customers and activities.</P>
                <HD SOURCE="HD2">B. Costs</HD>
                <HD SOURCE="HD3">1. One-Time Adjustment Costs to Banks</HD>
                <P>If adopted, the proposed rule would require alignment of existing AML/CFT programs to the clarified requirements, however these costs are expected to be minimal. Possible one-time costs include:</P>
                <FP SOURCE="FP-1">—Labor costs associated with updating policy, procedure, and documentation to reflect risk assessment processes, to codify definitions of “establish,” “maintain,” and “implement”, and to comply with the requirement that the program be written, accessible upon request, and approved by the board (or equivalent governance).</FP>
                <FP SOURCE="FP-1">—Potential labor costs or transitional productivity reductions associated with ensuring that the designated AML/CFT officer is located in the United States and has sufficient authority, stature, independence, and resourcing to comply with the requirements of the proposed rule.</FP>
                <FP SOURCE="FP-1">—Training costs to refresh relevant personnel to reflect the revised expectations, risk prioritization, updated governance roles, and program documentation.</FP>
                <P>
                    Given that most banks maintain AML/CFT programs that adhere with current regulations and supervisory expectations and given that the proposed rulemaking sets forth requirements that banks are already generally in compliance with, these incremental costs are expected to be minimal relative to current AML/CFT compliance costs. The Board does not have data available to estimate the one-time transition costs listed. In addition, the Board recognizes that these costs vary across banks based on their size, complexity, and the specific activities they engage in, as well as the sophistication of their current BSA compliance program.
                    <SU>69</SU>
                    <FTREF/>
                     Based on supervisory experience, Board staff believe that banks are already generally in compliance with the proposed requirements based on longstanding regulatory and supervisory expectations. Therefore, the Board anticipates that banks would expend 
                    <E T="03">de minimis</E>
                     incremental costs to update their AML/CFT compliance programs in conformance with the proposed requirements.
                </P>
                <FTNT>
                    <P>
                        <SU>69</SU>
                         The Board expects there would be variation in the magnitude of these transition costs among affected institutions, depending on bank size, complexity of business model, transaction volume, and scope and nature of products, customers, services, and geographical operations. Smaller institutions would be expected to have significantly less transition costs to update policies, procedures, and documentation than larger institutions with more complex risk profiles, higher transaction volume, and greater diversity and volume of products, customers, services, and geographical operations. Smaller institutions also tend to have significantly less staff dedicated to AML/CFT compliance than larger institutions. As such, these smaller institutions would need to train fewer staff on the proposed rule's requirements than larger institutions, requiring them to allocate fewer total dollars to training. Furthermore, smaller institutions generally already have a designated AML/CFT officer domiciled in the United States whereas larger, internationally active institutions may not. This would result in no expected labor opportunity costs for smaller institutions, but possibly one-time costs for larger internationally active institutions that do not currently have a U.S. domiciled AML/CFT officer.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Ongoing Costs to Banks</HD>
                <P>
                    While the Board lacks the data necessary to estimate how compliance costs for banks would change under the proposed rule, several factors suggest that ongoing compliance costs would be similar to the baseline.
                    <SU>70</SU>
                    <FTREF/>
                     First, banks already maintain extensive AML/CFT programs, in many cases exceeding the minimum requirements under current rules. Second, the proposed rule would clarify existing requirements rather than imposing new ones, which suggests that banks may not find it necessary to devote additional resources to AML/CFT programs relative to the baseline.
                </P>
                <FTNT>
                    <P>
                        <SU>70</SU>
                         The Board acknowledges that banks would have to incorporate any future AML/CFT priorities FinCEN issues as part of their ongoing costs. However, the Board believes that banks have already incorporated the current AML/CFT priorities into their BSA compliance programs because these “[p]riorities reflect longstanding and continuing AML/CFT concerns previously identified by FinCEN and other Treasury components and U.S. government departments and agencies” (see AML/CFT Priorities, page 3 (June 30, 2021)).
                    </P>
                </FTNT>
                <P>As a result, the Board anticipates no increase in ongoing compliance costs resulting from the proposed rule. Given the economic effects described above, the Board expects the benefits of the proposed rule would outweigh the costs.</P>
                <P>The Board invites comments on all aspects of the economic analysis provided in this supplemental information. What, if any, additional significant benefits or costs should the Board consider and why?</P>
                <HD SOURCE="HD1">VIII. Alternatives Considered</HD>
                <P>The Board has considered several alternatives to the proposed rule which could meet the objectives of this rulemaking. For the reasons described, the Board views the proposed rule as the most appropriate and effective means of achieving its policy objectives with respect to the Anti-Money Laundering Act of 2020.</P>
                <P>The Board considered taking no regulatory action. Under this alternative, banks would remain subject to separate, partially overlapping, and in some cases inconsistent AML/CFT program requirements across FinCEN and the Board. This would perpetuate regulatory fragmentation, increase compliance uncertainty, and risk inefficient resource allocation contrary to the AML Act's emphasis on risk-based programs. It would also fail to implement the AML Act's requirement that the AML/CFT Priorities be incorporated into program rules and examined accordingly, and it would not establish a uniform framework for distinguishing between program establishment and implementation. The Board therefore rejected this alternative.</P>
                <P>
                    The Board considered reissuing or finalizing the 2024 Notice of Proposed Rulemaking (2024 NPRM), which previously addressed these issues. However, public comments in response to the 2024 NPRM suggested that the 2024 NRPM did not adequately emphasize the increased flexibility of banks to recalibrate their BSA/AML programs to concentrate on higher-risk activities. In contrast, the proposed rule 
                    <PRTPAGE P="42379"/>
                    would provide such flexibility and, and as discussed in this section, result in greater benefits to the public. The proposed rule also includes provisions requiring FinCEN's consultation on supervisory actions and other measures to refocus supervision on substantive issues with bank AML/CFT programs rather than on procedural compliance. The Board therefore chose to issue the proposed rule.
                </P>
                <P>The Board considered developing more prescriptive program requirements, such as mandatory risk assessment methodologies, specific governance structures, required technologies, or defined timelines for updating risk assessments. Such an approach would conflict with the AML Act's emphasis on risk-based, flexible, and outcome oriented AML/CFT programs, and would be inconsistent with the Board's stated view that banks are best positioned to identify and evaluate their own risks. The Board therefore rejected this alternative in favor of a flexible framework aligned with statutory intent.</P>
                <P>The Board considered extending the implementation period beyond the proposed 12 months. A longer period would reduce near term adjustment costs for some banks but would delay the benefits of improved clarity, harmonization, and risk-based supervision. Given that most banks already maintain programs substantially consistent with the proposed requirements, the Board believes a 12 month period appropriately balances transition needs and timely realization of benefits.</P>
                <P>The Board considered whether the proposed rule should apply only to larger or more complex banks or include tailored requirements by size or business model. Because all banks must comply with the BSA, and because the proposal is inherently risk-based and scalable to each bank's risk profile, the Board determined that formal tailoring was unnecessary. Explicit tailoring could also undermine consistency and create cliff effects as banks restrict their growth to remain under regulatory thresholds. Therefore, the Board retained full applicability while emphasizing flexibility in program design.</P>
                <P>The Board invites comments on possible alternatives to the proposed rule.</P>
                <HD SOURCE="HD1">IX. Administrative Law Matters</HD>
                <HD SOURCE="HD2">A. Regulatory Flexibility Act (RFA)</HD>
                <P>
                    The Board is providing an initial regulatory flexibility analysis with respect to this proposal. The RFA requires an agency to consider whether the rules it proposes will have a significant economic impact on a substantial number of small entities. Under regulations issued by the SBA, a “small” entity includes a depository institution, bank holding company, or savings and loan holding company with total assets of $850 million or less.
                    <SU>71</SU>
                    <FTREF/>
                     For purposes of this section, any reference to “small” entities is a reference to this definition.
                </P>
                <FTNT>
                    <P>
                        <SU>71</SU>
                         
                        <E T="03">See</E>
                         13 CFR 121.201. Consistent with the SBA's General Principles of Affiliation, the Board includes the assets of all domestic and foreign affiliates toward the applicable size threshold when determining whether to classify a particular entity as a small entity. 
                        <E T="03">See</E>
                         13 CFR 121.103.
                    </P>
                </FTNT>
                <P>
                    In connection with a proposed rule, the RFA requires an agency to prepare an initial regulatory flexibility analysis describing the impact of the rule on small entities, unless the head of the agency certifies that the proposal will not have a significant economic impact on a substantial number of small entities and publishes such certification along with a statement providing the factual basis for such certification in the 
                    <E T="04">Federal Register</E>
                    . An initial regulatory flexibility analysis must contain (1) a description of the reasons why action by the agency is being considered; (2) a succinct statement of the objectives of, and legal basis for, the proposed rule; (3) a description of, and, where feasible, an estimate of the number of small entities to which the proposed rule will apply; (4) a description of the projected reporting, recordkeeping, and other compliance requirements of the proposed rule, including an estimate of the classes of small entities that will be subject to the requirement and the type of professional skills necessary for preparation of the report or record; (5) an identification, to the extent practicable, of all relevant Federal rules which may duplicate, overlap with, or conflict with the proposed rule; and (6) a description of any significant alternatives to the proposed rule which accomplish its stated objectives and minimize any significant economic impact of the proposed rule on small entities.
                    <SU>72</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>72</SU>
                         5 U.S.C. 603(b)-(c).
                    </P>
                </FTNT>
                <P>The Board has considered the potential impact of the proposal on small entities in accordance with the RFA. Based on its analysis and for the reasons stated below, the Board believes that this proposed rule will not have a significant economic impact on a substantial number of small entities. Nevertheless, the Board is publishing and inviting comment on this initial regulatory flexibility analysis.</P>
                <HD SOURCE="HD3">Reasons Why Action Is Being Considered by the Board</HD>
                <P>As explained above, the Board is proposing to amend its AML/CFT compliance program rule to align with changes that are being concurrently proposed by FinCEN and are required of FinCEN by the AML Act. The proposed rule would incorporate a risk assessment process in the Board's AML/CFT program rule that would require, among other things, consideration of the national AML/CFT Priorities published by FinCEN. It also would align other requirements, such as customer due diligence requirements, with FinCEN's rule and propose clarifying and other amendments to codify longstanding supervisory expectations.</P>
                <HD SOURCE="HD3">The Objectives of, and Legal Basis for, the Proposal</HD>
                <P>The Board's intent is to have AML/CFT program requirements for applicable institutions remain consistent with those imposed by FinCEN. Further, with consistent regulatory text, these institutions would not be subject to any additional burden or confusion from needing to comply with differing standards between FinCEN and the Board. The Board proposes to promulgate this rule pursuant to its safety and soundness authority and under section 8(s) of the Federal Deposit Insurance Act, 12 U.S.C. 1818(s), which requires the Board to issue regulations requiring supervised institutions to “establish and maintain procedures reasonably designed to assure and monitor the compliance” of the institutions with the requirements of the BSA.</P>
                <HD SOURCE="HD3">Estimate of the Number of Small Entities</HD>
                <P>
                    The proposal would apply to state member banks; Edge and agreement corporations; and branches, agencies, or representative offices of a foreign bank operating in the United States (other than a Federal branch or agency or a state branch that is insured by the FDIC) (“Board-supervised institutions”).
                    <SU>73</SU>
                    <FTREF/>
                     As of December 31, 2025, there were 703 insured State member banks, and approximately 439 Board-supervised institutions to which this proposed rule would apply that were small entities for purposes of the RFA.
                    <SU>74</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>73</SU>
                         12 CFR 208.63, 211.5(m), and 211.24(j).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>74</SU>
                         The small entity information is based on Call Report data as of December 31, 2025.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Description of the Compliance Requirements of the Proposal</HD>
                <P>
                    The proposed rule would revise 12 CFR 208.63 to require Board-supervised 
                    <PRTPAGE P="42380"/>
                    institutions to establish and maintain effective anti-money laundering and countering the financing of terrorism (AML/CFT) programs reasonably designed to identify, assess, and mitigate risks of illicit finance. Such a program must include: a risk assessment process that will serve as the basis for the AML/CFT program and includes, among other things, consideration of national AML/CFT priorities; one or more qualified AML/CFT compliance officers; policies, procedures and internal controls commensurate to address the bank's illicit finance risks; risk-based procedures for conducting ongoing CDD; an ongoing employee training program; and, independent, periodic AML/CFT program testing performed by qualified persons. The proposed rule would also incorporate a statutory requirement of the AML Act that persons with a duty of establishing, maintaining, and enforcing the AML/CFT program be in the United States and accessible to oversight and supervision by the appropriate regulator.
                </P>
                <P>
                    The Board estimates a rate of $51.20 per hour as the compensation associated with complying with the proposed rule.
                    <SU>75</SU>
                    <FTREF/>
                     The estimated cost and burden to comply with the requirement to update programs to incorporate the new definition of “AML/CFT program” would be minimal, as this is essentially a change in terminology. Likewise, complying with the additional regulatory requirement to conduct a risk assessment incorporating the AML/CFT priorities would not impose significant additional burden because this is an existing, longstanding supervisory expectation for Board-supervised institutions and because the priorities reflect longstanding AML/CFT concerns previously identified by FinCEN and governmental agencies.
                    <SU>76</SU>
                    <FTREF/>
                     Accordingly, Board-supervised institutions should already have a risk assessment incorporating the AML/CFT priorities and the other components of the proposed rule in place. The Board estimates that the additional burden associated with these minimal changes on small entities to be approximately $760,218 (32 hours × $51.20 per hour × 464 small entities) in the first year after adoption, and approximately $190,054 (8 hours × $51.20 per hour × 464 small entities) in each successive year.
                </P>
                <FTNT>
                    <P>
                        <SU>75</SU>
                         To estimate hourly compensation, the assumed distribution of occupation groups involved in the actions taken by institutions in response to the proposed rule in year 1 and in subsequent years include Executives and Managers (1 percent of hours), Compliance Officers (29 percent), and Clerical (70 percent). This combination of occupations results in an overall estimated hourly total compensation rate of $51.20. This average rate is derived from the U.S. Bureau of Labor Statistics (BLS) Specific Occupational Employment and Wage Estimates for May 2023, and March 2023 BLS Cost of Employee Compensation data for the Employment Cost Index between March 2023 and March 2024.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>76</SU>
                         AML/CFT Priorities, page 3 (June 30, 2021).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Consideration of Duplicative, Overlapping, or Conflicting Rules and Significant Alternatives to the Proposal</HD>
                <P>The Board has not identified any Federal statutes or regulations that would duplicate, overlap, or conflict with the proposal, other than FinCEN's proposed AML/CFT program rule, described above. In addition, the Board considered the alternative of leaving its program rule unrevised but determined not to do so, for the reasons explained in the Alternatives section above.</P>
                <HD SOURCE="HD3">Conclusion</HD>
                <P>Based on its analysis and for the reasons stated above, the Board believes that the proposal is unlikely to have a significant economic impact on substantial number of small entities supervised by the Board. The Board welcomes comment on all aspects of its analysis. In particular, the Board requests that commenters describe the nature of any impact on small entities and provide empirical data to illustrate and support the extent of the impact. Additionally, the Board requests that commenters describe the number of small entities under the RFA and the impact on small entities.</P>
                <HD SOURCE="HD2">B. Paperwork Reduction Act (PRA)</HD>
                <P>
                    The Paperwork Reduction Act of 1995 
                    <SU>77</SU>
                    <FTREF/>
                     (PRA) states that no agency may conduct or sponsor, nor is the respondent required to respond to, an information collection unless it displays a currently valid Office of Management and Budget (OMB) control number. The Board has reviewed this proposed rule and determined that it does not create any information collection. The Board reviewed the proposed rule under the authority delegated to the Board by OMB.
                </P>
                <FTNT>
                    <P>
                        <SU>77</SU>
                         44 U.S.C. 3501-3521.
                    </P>
                </FTNT>
                <P>
                    Comments on aspects of this document that may affect reporting, recordkeeping, or disclosure requirements and burden estimates should be sent to the addresses listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. Written comments and recommendations for these information collections also should be sent within 30 days of publication of this document to 
                    <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                     Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                </P>
                <HD SOURCE="HD2">C. Riegle Community Development and Regulatory Improvement Act</HD>
                <P>
                    Pursuant to section 302(a) of the Riegle Community Development and Regulatory Improvement Act of 1994 (RCDRIA),
                    <SU>78</SU>
                    <FTREF/>
                     in determining the effective date and administrative compliance requirements for new regulations that impose additional reporting, disclosure, or other requirements on IDIs, each Federal banking agency must consider, consistent with principles of safety and soundness and the public interest, any administrative burdens that such regulations would place on affected depository institutions, including small depository institutions, and customers of depository institutions, as well as the benefits of such regulations. In addition, section 302(b) of the RCDRIA requires new regulations and amendments to regulations that impose additional reporting, disclosures, or other new requirements on IDIs generally to take effect on the first day of a calendar quarter that begins on or after the date on which the regulations are published in final form. The Board invites comments that further will inform its consideration of the RCDRIA.
                    <SU>79</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>78</SU>
                         12 U.S.C. 4802(a).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>79</SU>
                         12 U.S.C. 4802(b).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. Plain Language</HD>
                <P>
                    Section 722 of the Gramm-Leach-Bliley Act 
                    <SU>80</SU>
                    <FTREF/>
                     requires the Federal banking agencies to use plain language in all proposed and final rulemakings published in the 
                    <E T="04">Federal Register</E>
                     after January 1, 2000. The Board invites your comments on how to make this proposed rule easier to understand. For example:
                </P>
                <FTNT>
                    <P>
                        <SU>80</SU>
                         Public Law 106-102, section 722, 113 Stat. 1338, 1471 (1999), 12 U.S.C. 4809.
                    </P>
                </FTNT>
                <P>• Has the Board organized the material to suit your needs? If not, how could the proposed rule be more clearly stated?</P>
                <P>• Are the requirements in the proposed rule clearly stated? If not, how could the proposed rule be more clearly stated?</P>
                <P>• Does the proposed rule contain language or jargon that is not clear? If so, which language requires clarification?</P>
                <P>• Would a different format (grouping and order of sections, use of headings, paragraphing) make the proposed rule easier to understand? If so, what changes to the format would make the proposed rule easier to understand?</P>
                <P>
                    • What else could the Board do to make the proposed rule easier to understand?
                    <PRTPAGE P="42381"/>
                </P>
                <HD SOURCE="HD2">E. Providing Accountability Through Transparency Act of 2023</HD>
                <P>
                    The Providing Accountability Through Transparency Act of 2023 requires that a notice of proposed rulemaking include the internet address of a summary of not more than 100 words in length of a proposed rule, in plain language, that shall be posted on the internet website under section 206(d) of the E-Government Act of 2002.
                    <SU>81</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>81</SU>
                         44 U.S.C. 3501 note.
                    </P>
                </FTNT>
                <P>
                    The proposal and the required summary can be found for the Board at 
                    <E T="03">https://www.federalreserve.gov/apps/foia/proposedregs.aspx.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 12 CFR Part 208</HD>
                    <P>Accounting, Agriculture, Banks, Banking, Confidential business information, Consumer protection, Crime, Currency, Federal Reserve System, Flood insurance, Insurance, Investments, Mortgages, Reporting and recordkeeping requirements, Securities.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Authority and Issuance</HD>
                <P>For the reasons set forth in the preamble, the Board of Governors of the Federal Reserve System proposes to amend 12 CFR part 208 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 208—MEMBERSHIP OF STATE BANKING INSTITUTIONS IN THE FEDERAL RESERVE SYSTEM (REGULATION H)</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 208 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 2 U.S.C. 24, 36, 92a, 93a, 248(a), 248(c), 321-338a, 371d, 461, 481-486, 601, 611, 1814, 1816, 1817(a)(3), 1817(a)(12), 1818, 1820(d)(9), 1833(j), 1828(o), 1831, 1831o, 1831p-1, 1831r-1, 1831w, 1831x, 1835a, 1882, 2901-2907, 3105, 3310, 3331-3351, 3905-3909, 5371, and 5371 note; 15 U.S.C. 78b, 78I(b), 78l(i), 780-4(c)(5), 78q, 78q-1, 78w, 1681s, 1681w, 6801, and 6805; 31 U.S.C. 5318; 42 U.S.C. 4012a, 4104a, 4104b, 4106, and 4128.</P>
                </AUTH>
                <AMDPAR>2. Revise § 12 CFR 208.63 and republish to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 208.63 </SECTNO>
                    <SUBJECT>Anti-Money Laundering/Countering the Financing of Terrorism Compliance, Supervision, and Enforcement</SUBJECT>
                    <P>
                        (a) 
                        <E T="03">Definitions.</E>
                         For purposes of this section:
                    </P>
                    <P>
                        (1) 
                        <E T="03">AML/CFT enforcement action</E>
                         means any formal or informal action taken by the Board under authority of 12 U.S.C. 1818 or other applicable law that seeks to penalize, remedy, prevent, or respond to noncompliance with past or ongoing violations of, or past or ongoing deficiencies relating to, an AML/CFT requirement. The term includes—
                    </P>
                    <P>(i) A cease-and-desist order, written agreement, consent order, or memorandum of understanding; or</P>
                    <P>(ii) The assessment of a civil money penalty.</P>
                    <P>
                        (2) 
                        <E T="03">AML/CFT requirement</E>
                         means:
                    </P>
                    <P>(i) A requirement of the Bank Secrecy Act or the implementing regulations at 31 CFR chapter X; or</P>
                    <P>(ii) A requirement prescribed under 12 U.S.C. 1818(s) or this section.</P>
                    <P>
                        (3) 
                        <E T="03">Bank Secrecy Act</E>
                         has the meaning given that term in 31 CFR 1010.100.
                    </P>
                    <P>
                        (4) 
                        <E T="03">Significant AML/CFT supervisory action</E>
                         means any written communication or other formal supervisory determination that—
                    </P>
                    <P>(i) Identifies one or more alleged deficiencies, weaknesses, violations of law, or unsafe or unsound practices or conditions relating to an AML/CFT requirement;</P>
                    <P>(ii) Communicates supervisory expectations to a state member bank regarding actions or remedial measures required to correct the deficiency, weakness, violation, or practice or condition; and</P>
                    <P>(iii) Contemplates significant or programmatic actions or remedial measures to be taken by the state member bank.</P>
                    <P>The term does not include examiner observations, suggestions, or other informal comments.</P>
                    <P>
                        (b) 
                        <E T="03">AML/CFT program in general.</E>
                         Each state member bank must establish and maintain an effective AML/CFT program. A state member bank complies with this requirement if it:
                    </P>
                    <P>(1) Establishes an AML/CFT program in accordance with paragraph (c) of this section; and</P>
                    <P>(2) Maintains an AML/CFT program by implementing the AML/CFT program in accordance with paragraph (d) of this section.</P>
                    <P>
                        (c) 
                        <E T="03">AML/CFT program establishment.</E>
                         A state member bank establishes an AML/CFT program in accordance with this paragraph if it:
                    </P>
                    <P>(1) Establishes a risk-based set of internal policies, procedures, and controls that is reasonably designed to ensure compliance with the Bank Secrecy Act and the implementing regulations at 31 CFR chapter X and to:</P>
                    <P>(i) Identify, assess, and document the state member bank's money laundering, terrorist financing, and other illicit finance activity risks through risk assessment processes that:</P>
                    <P>(A) Evaluate the money laundering, terrorist financing, and other illicit finance activity risks of the state member bank's business activities, including its products, services, distribution channels, customers, and geographic locations;</P>
                    <P>(B) Review and, as appropriate, incorporate the AML/CFT priorities as that term is defined in 31 CFR 1010.100; and</P>
                    <P>(C) Are updated promptly upon any change that the state member bank knows or has reason to know significantly changes the state member bank's money laundering, terrorist financing, and other illicit finance activity risks;</P>
                    <P>(ii) Mitigate the state member bank's money laundering, terrorist financing, and other illicit finance activity risks consistent with the risk assessment processes required under paragraph (c)(1)(i) of this section, including by directing more attention and resources toward higher-risk customers and activities, consistent with the risk profile of the state member bank, rather than toward lower-risk customers and activities; and</P>
                    <P>(iii) Conduct ongoing customer due diligence, including to:</P>
                    <P>(A) Understand the nature and purpose of customer relationships for the purpose of developing a customer risk profile; and</P>
                    <P>(B) Conduct ongoing monitoring to identify and report suspicious transactions and, on a risk basis, to maintain and update customer information (including information regarding the beneficial owners of legal entity customers, as defined in 31 CFR 1010.230);</P>
                    <P>(2) Establishes independent AML/CFT program testing to be conducted by bank personnel or by an outside party;</P>
                    <P>(3) Designates an individual, who is (i) located in the United States, (ii) accessible to, and subject to oversight and supervision by, FinCEN and the Board, and (iii) responsible for establishing and implementing the AML/CFT program and coordinating and monitoring day-to-day compliance; and</P>
                    <P>(4) Establishes an ongoing employee training program.</P>
                    <P>
                        (d) 
                        <E T="03">AML/CFT program implementation.</E>
                         A state member bank implements an AML/CFT program in accordance with this paragraph if the state member bank implements, in all material respects, the AML/CFT program required under paragraph (c) of this section.
                    </P>
                    <P>
                        (e) 
                        <E T="03">Written AML/CFT program and approval.</E>
                         A state member bank's AML/CFT program must be written and it must be approved by the state member bank's board of directors, an equivalent governing body within the state member bank, or appropriate senior management within the state member bank.
                    </P>
                    <P>
                        (f) 
                        <E T="03">Customer identification program.</E>
                         Each state member bank shall 
                        <PRTPAGE P="42382"/>
                        implement a customer identification program in accordance with 31 CFR 1020.220.
                    </P>
                    <P>
                        (g) 
                        <E T="03">Enforcement and supervision policy.</E>
                    </P>
                    <P>
                        (1) 
                        <E T="03">In general.</E>
                         Except with respect to a significant or systemic failure to implement the AML/CFT program in accordance with paragraph (d) of this section, a state member bank that has established an AML/CFT program in accordance with paragraph (c) of this section will not be subject to an AML/CFT enforcement action or to a significant AML/CFT supervisory action related to the requirements of 12 U.S.C. 1818(s), 31 U.S.C. 5318(h)(1), this section, or 31 CFR 1020.210.
                    </P>
                    <P>
                        (2) 
                        <E T="03">Program establishment violations.</E>
                         Nothing in this paragraph (g) may be construed to restrict an AML/CFT enforcement action or a significant AML/CFT supervisory action with respect to any failure to establish an AML/CFT program in accordance with paragraph (c) of this section.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Criminal Enforcement Unaffected.</E>
                         Nothing in this paragraph (g) may be construed to affect criminal enforcement under the BSA.
                    </P>
                    <P>(h) Severability.</P>
                    <P>The provisions of this section are separate and severable from one another. If any provision of this section is held to be invalid, or the application thereof to any person or circumstance is held to be invalid, such invalidity shall not affect other provisions, or application of such provisions to other persons or circumstances, that can be given effect without the invalid provision or application.</P>
                </SECTION>
                <SIG>
                    <P>By order of the Board of Governors of the Federal Reserve System.</P>
                    <NAME>Benjamin McDonough,</NAME>
                    <TITLE>Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13919 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">CONSUMER FINANCIAL PROTECTION BUREAU</AGENCY>
                <CFR>12 CFR Parts 1024 and 1026</CFR>
                <DEPDOC>[Docket No. CFPB-2026-0018]</DEPDOC>
                <SUBJECT>Request for Information Regarding Promoting Access to Mortgage Credit</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Consumer Financial Protection Bureau.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice requests information from the public about potential regulatory changes that may reduce regulatory burdens and promote access to mortgage credit, as appropriate and consistent with applicable law. The Consumer Financial Protection Bureau (Bureau or CFPB) seeks to reduce unwarranted regulatory burdens to ensure that creditworthy borrowers can access mortgage credit. Specifically, the CFPB is requesting information on industry and consumer burdens related to the integrated mortgage disclosures under the Truth in Lending Act (TILA) and Real Estate Settlement Procedures Act (RESPA) (TILA-RESPA integrated disclosures or TRID), the right of rescission, and reverse mortgage disclosures.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before August 10, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by Docket No. CFPB-2026-0018, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: https://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Email: 2026-RFI-Mortgage-Disclosures-and-Rescission@cfpb.gov.</E>
                         Include Docket No. CFPB-2026-0018 in the subject line of the message.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail/Hand Delivery/Courier:</E>
                         Comment Intake—Mortgage Disclosures and Rescission RFI, c/o Legal Division Docket Manager, Consumer Financial Protection Bureau, 445 12th St. SW, Washington, DC 20024-2101.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         The Bureau encourages the early submission of comments. All submissions must include the document title and docket number. Please note the number of the topic on which you are commenting at the top of each response (you do not need to address all topics). Because paper mail in the Washington, DC area and at the CFPB is subject to delay, commenters are encouraged to submit comments electronically. In general, all comments received will be posted without change to 
                        <E T="03">www.regulations.gov.</E>
                    </P>
                    <P>All submissions in response to this request for information, including attachments and other supporting materials, will become part of the public record and subject to public disclosure. Proprietary information or sensitive personal information, such as account numbers or Social Security numbers, or names of other individuals, should not be included. Submissions will not be edited to remove any identifying or contact information.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Dave Gettler, Paralegal Specialist, Office of Regulations, at 202-435-7700. If you require this document in an alternative electronic format, please contact 
                        <E T="03">CFPB_Accessibility@cfpb.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Summary of the Notice and Request for Information</HD>
                <HD SOURCE="HD2">A. Executive Order 14393—Promoting Access to Mortgage Credit</HD>
                <P>
                    On March 13, 2026, the President issued Executive Order (E.O.) 14393, entitled “Promoting Access to Mortgage Credit.” 
                    <SU>1</SU>
                    <FTREF/>
                     E.O. 14393 provides, in part, that statutory and regulatory changes “have increased the compliance costs of mortgage origination” and “contributed to a significant decline in [community] bank participation in mortgage lending.” 
                    <SU>2</SU>
                    <FTREF/>
                     E.O. 14393 states that the regulatory and rule changes have “resulted in reduced access to credit for some creditworthy borrowers.” 
                    <SU>3</SU>
                    <FTREF/>
                     E.O. 14393 provides that it is the policy of the United States to, among other things, “improve the availability and affordability of mortgage credit,” “facilitate community bank engagement in mortgage activity,” and “modernize origination and closing standards to reduce lending costs.” 
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         91 FR 13203 (Mar. 18, 2026).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>Section 2 of E.O. 14393 states, in part, that the CFPB “shall consider, as appropriate and consistent with applicable law:</P>
                <EXTRACT>
                    <P>(i) proposing amendments to Regulation Z that tailor the following requirements for smaller banks: ATR and QM requirements (including potentially a broader QM safe harbor for portfolio loans) and the requirements of the Truth in Lending Act, Public Law 90-321 (TILA), Real Estate Settlement Procedure[s] Act, Public Law 93-533 (RESPA), and TILA-RESPA Integrated Disclosure (TRID) rules;</P>
                    <P>(ii) replacing TRID timing rules with a materiality-based standard that preserves consumer clarity and reduces closing delays; [and]</P>
                    <P>. . . .</P>
                    <P>
                        (vii) exempting rate-and-term refinancing (including cash-out refinancing) from rescission rights.” 
                        <SU>5</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             
                            <E T="03">Id.</E>
                             at 13203-04.
                        </P>
                    </FTNT>
                </EXTRACT>
                <P>
                    The CFPB recognizes certain regulations may contribute to higher costs for borrowers needing access to mortgage credit. Consistent with E.O. 14393 and the CFPB's express objective to ensure “outdated, unnecessary, or unduly burdensome regulations are regularly identified and addressed in order to reduce unwarranted regulatory burdens,” 
                    <SU>6</SU>
                    <FTREF/>
                     the CFPB is issuing this notice.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         12 U.S.C. 5511(b)(3).
                    </P>
                </FTNT>
                <PRTPAGE P="42383"/>
                <HD SOURCE="HD2">B. TILA-RESPA Integrated Disclosures</HD>
                <HD SOURCE="HD3">Background</HD>
                <P>
                    In 2013, as required by sections 1098 and 1100A of the Dodd-Frank Wall Street Reform and Consumer Protection Act (Dodd-Frank Act),
                    <SU>7</SU>
                    <FTREF/>
                     the CFPB issued the Integrated Mortgage Disclosures under the Real Estate Settlement Procedures Act (Regulation X) and the Truth in Lending Act (Regulation Z) final rule (2013 final rule).
                    <SU>8</SU>
                    <FTREF/>
                     The CFPB has since finalized amendments to the 2013 final rule, including in 2015 (twice), 2017, and 2018.
                    <SU>9</SU>
                    <FTREF/>
                     The 2013 final rule and subsequent amendments to that rule are referred to collectively herein as the TRID Rule.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Public Law 111-203, 124 Stat. 1376, 2103-04, 2107-09 (2010) (codified at 12 U.S.C. 2603(a) and 15 U.S.C. 1604(b)).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         78 FR 79730 (Dec. 31, 2013).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         80 FR 8767 (Feb. 19, 2015); 80 FR 43911 (July 24, 2015); 82 FR 37656 (Aug. 11, 2017); 83 FR 19159 (May 2, 2018).
                    </P>
                </FTNT>
                <P>
                    On November 22, 2019, the CFPB published a request for information (RFI) in the 
                    <E T="04">Federal Register</E>
                     as part of its assessment of the TRID Rule's effectiveness and invited the public to submit comments and information on a variety of topics.
                    <SU>10</SU>
                    <FTREF/>
                     On October 1, 2020, the CFPB issued its TRID Rule Assessment Report,
                    <SU>11</SU>
                    <FTREF/>
                     which describes the comments and summarizes the information received. The full comments are available at 
                    <E T="03">https://www.regulations.gov/document/CFPB-2019-0055-0001/comment.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         84 FR 64436 (Nov. 22, 2019).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Consumer Fin. Prot. Bureau, 
                        <E T="03">Integrated Mortgage Disclosures Under the Real Estate Settlement Procedures Act (Regulation X) and the Truth in Lending Act (Regulation Z) Rule Assessment Report</E>
                         (Oct. 2020) (Assessment Report), 
                        <E T="03">https://files.consumerfinance.gov/f/documents/cfpb_trid-rule-assessment_report.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Scope of the TRID Rule</HD>
                <P>
                    The TRID Rule generally requires creditors to provide the Loan Estimate and Closing Disclosure forms for closed-end consumer credit transactions secured by real property or a cooperative unit, other than reverse mortgages.
                    <SU>12</SU>
                    <FTREF/>
                     Rather than adopting a small creditor exemption, such as one based on asset size, the TRID Rule retained the existing volume-based exemptions in Regulation Z.
                    <SU>13</SU>
                    <FTREF/>
                     In particular, Regulation Z defines “creditor,” in pertinent part, as a person who regularly extends consumer credit.
                    <SU>14</SU>
                    <FTREF/>
                     Regulation Z further provides that a person regularly extends consumer credit only if it extended credit (other than high-cost mortgages) more than 25 times (or more than five times for transactions secured by a dwelling) in the preceding calendar year.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         12 CFR 1026.19(e)(1)(i) and (f)(1)(i).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         78 FR 79730, 79771 (Dec. 31, 2013).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Id.</E>
                         at 79789 (citing 12 CFR 1026.2(a)(17)(i)).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         12 CFR 1026.2(a)(17)(v). Regulation Z provides that if a person did not meet these numerical standards in the preceding calendar year, the numerical standards shall be applied to the current calendar year. 
                        <E T="03">Id.</E>
                         Regulation Z also provides that a person regularly extends consumer credit if, in any 12-month period, the person originates more than one high-cost mortgage or one or more such credit extensions through a mortgage broker. 
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>The following is an overview of the Loan Estimate and Closing Disclosure forms and accuracy and timing standards applicable to each.</P>
                <HD SOURCE="HD3">Loan Estimate</HD>
                <P>
                    The Loan Estimate form integrates disclosures under the TILA and RESPA statutes, as required by the Dodd-Frank Act.
                    <SU>16</SU>
                    <FTREF/>
                     For example, the Loan Estimate integrates the early TILA disclosures provided near the time of application and the RESPA Good Faith Estimate (GFE).
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         12 U.S.C. 2603(a); 15 U.S.C. 1604(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         78 FR 79730, 79907-08 (Dec. 31, 2013).
                    </P>
                </FTNT>
                <P>
                    The Loan Estimate may be provided to the consumer in electronic form,
                    <SU>18</SU>
                    <FTREF/>
                     subject to compliance with the statutory provisions of the Electronic Signatures in Global and National Commerce Act (E-Sign Act).
                    <SU>19</SU>
                    <FTREF/>
                     The E-Sign Act provides that electronic documents and electronic signatures have the same validity as paper documents and handwritten signatures—and that disclosures may be provided in electronic form if the consumer affirmatively consents after receiving a notice and if certain other conditions are met. The TRID Rule does not 
                    <E T="03">require</E>
                     consumers to sign Loan Estimates, but it provides creditors the 
                    <E T="03">option</E>
                     to include a line for consumer signatures to acknowledge receipt.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         12 CFR 1026.37(o)(3)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         15 U.S.C. 7001 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         12 CFR 1026.37(n).
                    </P>
                </FTNT>
                <P>
                    In accordance with TILA,
                    <SU>21</SU>
                    <FTREF/>
                     mailed disclosures are presumed to be received by the consumer three business days after mailing.
                    <SU>22</SU>
                    <FTREF/>
                     If the creditor has evidence that the consumer received the disclosures earlier, the creditor may rely on that evidence and consider it to be received on that earlier date.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         15 U.S.C. 1638(b)(2)(E).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         12 CFR 1026.19(e)(1)(iv).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         Regulation Z comment 19(e)(1)(iv)-2.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Good Faith</HD>
                <P>
                    TILA requires that “good faith” estimates of disclosures on the Loan Estimate must be delivered or placed in the mail within three business days of application.
                    <SU>24</SU>
                    <FTREF/>
                     RESPA similarly requires that “good faith” estimates of settlement costs must be provided within three business days of application.
                    <SU>25</SU>
                    <FTREF/>
                     The TRID Rule provides bright-line tolerance standards for the objective determination of whether the estimates were made in “good faith.” 
                    <SU>26</SU>
                    <FTREF/>
                     If the consumer is ultimately charged more than the applicable tolerances because of changed circumstances, the TRID Rule also permits creditors to reset the tolerances with revised estimates as discussed below.
                    <SU>27</SU>
                    <FTREF/>
                     As discussed in the TRID Rule preamble, these tolerance standards are similar to preexisting Regulation X disclosure standards that implement RESPA.
                    <SU>28</SU>
                    <FTREF/>
                     Moreover, TILA generally authorizes the CFPB to adopt tolerances necessary to facilitate compliance with the statute, provided such tolerances are narrow enough to prevent misleading disclosures or disclosures that circumvent the purposes of the statute.
                    <SU>29</SU>
                    <FTREF/>
                     The TRID Rule preamble states that the rule's tolerances “are appropriate, will facilitate compliance with the statute by providing bright-line rules for the determination of `good faith' based on the knowledge of costs that creditors have, or reasonably should have, and prevent misleading disclosures.” 
                    <SU>30</SU>
                    <FTREF/>
                     The TRID Rule preamble further states that the rule's tolerances “will effectuate the statute's goals by ensuring more reliable estimates, which will increase the level of shopping for mortgage loans and foster honest competition for prospective consumers among financial institutions.” 
                    <SU>31</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         15 U.S.C. 1638(b)(2)(A); 
                        <E T="03">see also</E>
                         12 CFR 1026.19(e)(1)(iii)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         12 U.S.C. 2604.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         12 CFR 1026.19(e)(3).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         78 FR 79730, 79818 (Dec. 31, 2013).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         15 U.S.C. 1631(d).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         78 FR 79730, 79822 (Dec. 31, 2013).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Zero Tolerance</HD>
                <P>
                    Estimates of charges paid to creditors or mortgage brokers (or their affiliates) and transfer taxes are in good faith if the consumer is not charged more than the estimates. Estimates of third-party charges are also subject to zero tolerance if the creditor requires the consumer to use 
                    <E T="03">creditor-selected</E>
                     service providers (rather than permitting the consumer to shop for third-party service providers).
                    <SU>32</SU>
                    <FTREF/>
                     In response to the November 2019 RFI, several commenters stated that transfer taxes and third-party appraisal fees are particularly difficult for creditors to estimate within three business days of application and that the CFPB should 
                    <PRTPAGE P="42384"/>
                    not include these fees in the zero tolerance category.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         12 CFR 1026.19(e)(3)(i).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         Assessment Report at 192.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">10 Percent Tolerance</HD>
                <P>
                    Estimates of recording fees and certain third-party charges are deemed to have been made in good faith when the creditor permits the consumer to shop for third-party service providers if, in the aggregate, the consumer is charged no more than 10 percent in excess of the estimates.
                    <SU>34</SU>
                    <FTREF/>
                     Specifically, estimates of unaffiliated third-party charges are subject to the 10 percent tolerance if the creditor 
                    <E T="03">permits</E>
                     the consumer to shop for that service, but nonetheless the consumer either does not choose a provider, or chooses a provider identified by the creditor.
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         12 CFR 1026.19(e)(3)(ii).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Unlimited Tolerance</HD>
                <P>
                    Estimates of other third-party charges are in good faith—regardless of how much the consumer is charged—if the consumer chooses a third-party service provider that is 
                    <E T="03">not</E>
                     on the creditor's list of providers (so long as the estimate was based on the best information reasonably available). Estimates of prepaid interest, property insurance premiums, escrowed amounts, property taxes, and charges for non-required services similarly have no tolerance limit.
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         12 CFR 1026.19(e)(3)(iii).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Seven-Business-Day Waiting Period</HD>
                <P>
                    As required by TILA,
                    <SU>36</SU>
                    <FTREF/>
                     the Loan Estimate must be delivered or placed in the mail not later than seven business days prior to consummation.
                    <SU>37</SU>
                    <FTREF/>
                     After receiving the Loan Estimate, in accordance with TILA,
                    <SU>38</SU>
                    <FTREF/>
                     the consumer may waive the seven-business-day waiting period for a bona fide personal financial emergency.
                    <SU>39</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         15 U.S.C. 1638(b)(2)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         12 CFR 1026.19(e)(1)(iii)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         15 U.S.C. 1638(b)(2)(F).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         12 CFR 1026.19(e)(1)(v).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Revised Estimates</HD>
                <P>
                    As noted above, TILA requires initial “good faith” estimates within three business days of application—and the TRID Rule provides bright-line tolerance standards for the determination of “good faith.” If the consumer is charged more than the tolerances (
                    <E T="03">e.g.,</E>
                     zero or 10 percent tolerances), the TRID Rule also permits creditors to 
                    <E T="03">reset</E>
                     the tolerances with revised estimates if they are provided within three business days of receipt of information necessitating the revision (
                    <E T="03">i.e.,</E>
                     changed circumstance).
                    <SU>40</SU>
                    <FTREF/>
                     In response to the November 2019 RFI, several commenters stated that tracking such changes and issuing revised estimates to the consumer within three business days is unduly burdensome.
                    <SU>41</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         12 CFR 1026.19(e)(3) and (4).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         Assessment Report at 193.
                    </P>
                </FTNT>
                <P>
                    The TRID Rule prohibits providing revised Loan Estimates on or after the date on which the creditor provides the Closing Disclosure form.
                    <SU>42</SU>
                    <FTREF/>
                     Accordingly, the TRID Rule also permits creditors to 
                    <E T="03">reset</E>
                     tolerances (
                    <E T="03">e.g.,</E>
                     zero or 10 percent tolerances) with a Closing Disclosure if it is provided within three business days of receipt of information necessitating the revision (
                    <E T="03">i.e.,</E>
                     changed circumstance).
                    <SU>43</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         12 CFR 1026.19(e)(4)(ii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         12 CFR 1026.19(e)(3) and (4).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Closing Disclosure</HD>
                <P>
                    The Closing Disclosure form integrates the final TILA disclosures and the RESPA Settlement Statement (HUD-1), as required by the Dodd-Frank Act.
                    <SU>44</SU>
                    <FTREF/>
                     The Closing Disclosure may be provided to the consumer in electronic form,
                    <SU>45</SU>
                    <FTREF/>
                     subject to compliance with the statutory provisions of the E-Sign Act as noted above.
                    <SU>46</SU>
                    <FTREF/>
                     The TRID Rule does not require consumers to sign the Closing Disclosure, but it provides creditors the 
                    <E T="03">option</E>
                     to include a line for consumer signatures to acknowledge receipt.
                    <SU>47</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         12 U.S.C. 2603(a); 15 U.S.C. 1604(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         12 CFR 1026.38(t)(3)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         15 U.S.C. 7001 
                        <E T="03">et seq.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         12 CFR 1026.38(s).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Three-Business-Day Waiting Period</HD>
                <P>
                    The consumer must receive the Closing Disclosure no later than three business days before consummation.
                    <SU>48</SU>
                    <FTREF/>
                     TILA generally requires that, if the annual percentage rate (APR) disclosed in the early TILA disclosures becomes inaccurate (subject to an APR tolerance of 0.125 percent for most loans), the creditor must provide corrected disclosures to the consumer no later than three business days before consummation.
                    <SU>49</SU>
                    <FTREF/>
                     After receiving the Closing Disclosure, in accordance with TILA,
                    <SU>50</SU>
                    <FTREF/>
                     the consumer may waive the three-business-day waiting period for a bona fide personal financial emergency.
                    <SU>51</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         12 CFR 1026.19(f)(1)(ii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         15 U.S.C. 1638(b)(2)(D); 15 U.S.C. 1606(c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         15 U.S.C. 1638(b)(2)(F).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         12 CFR 1026.19(f)(1)(iv).
                    </P>
                </FTNT>
                <P>
                    A new three-business-day waiting period is required if one of the following events occurs: (1) the APR becomes inaccurate,
                    <SU>52</SU>
                    <FTREF/>
                     subject to APR tolerances discussed above and in accordance with TILA; 
                    <SU>53</SU>
                    <FTREF/>
                     (2) the loan product changes; 
                    <SU>54</SU>
                    <FTREF/>
                     or (3) a prepayment penalty is added.
                    <SU>55</SU>
                    <FTREF/>
                     In accordance with TILA,
                    <SU>56</SU>
                    <FTREF/>
                     the consumer may similarly waive the new three-business-day waiting period for a bona fide personal financial emergency.
                    <SU>57</SU>
                    <FTREF/>
                     For other changes besides the three types of changes listed above, a new three-business-day waiting period is not required (but the consumer must receive a corrected Closing Disclosure at or before consummation).
                    <SU>58</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         12 CFR 1026.19(f)(2)(ii)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         15 U.S.C. 1638(b)(2)(D); 15 U.S.C. 1606(c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         12 CFR 1026.19(f)(2)(ii)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         12 CFR 1026.19(f)(2)(ii)(C).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         15 U.S.C. 1638(b)(2)(F).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         12 CFR 1026.19(f)(1)(iv).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         12 CFR 1026.19(f)(2)(i).
                    </P>
                </FTNT>
                <P>
                    In response to the November 2019 RFI, several commenters stated that the CFPB should provide additional guidance or otherwise streamline consumers' ability to waive the Closing Disclosure three-business-day waiting period.
                    <SU>59</SU>
                    <FTREF/>
                     For refinancing transactions for which there is a three-business-day rescission period after consummation under TILA, several commenters stated that requiring a three-business-day waiting period before consummation is redundant and an undue burden.
                    <SU>60</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         Assessment Report at 187.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>60</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Right of Rescission</HD>
                <P>
                    TILA established a consumer's statutory right to rescind most transactions for which the home is taken as collateral, other than transactions for the purchase of the home.
                    <SU>61</SU>
                    <FTREF/>
                     TILA and Regulation Z provide consumers with a three-day period to rescind a consummated agreement for any reason.
                    <SU>62</SU>
                    <FTREF/>
                     The rescission period begins after the last of three events: consummation of the transaction; delivery of all material disclosures; and delivery to the consumer of the required rescission notice. No money may be disbursed other than in escrow, no services may be performed, and no materials may be delivered until the rescission period has expired and the creditor is reasonably satisfied that the consumer has not rescinded.
                    <SU>63</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>61</SU>
                         Public Law 90-321, tit. I, section 125, 82 Stat. 153 (1968).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>62</SU>
                         15 U.S.C. 1635(a); 12 CFR 1026.23(a). The rescission period may be extended up to three years if the creditor fails to disclose, or improperly discloses, certain TILA requirements. 
                        <E T="03">See</E>
                         15 U.S.C. 1635(f) and 12 CFR 1026.23(a).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>63</SU>
                         12 CFR 1026.23(c).
                    </P>
                </FTNT>
                <P>
                    Provided a consumer has not waived the right of rescission to meet a bona fide personal financial emergency,
                    <SU>64</SU>
                    <FTREF/>
                     the three-day post-consummation rescission waiting period, coupled with the three-day pre-consummation TRID waiting period, means that a consumer whose loan is subject to rescission has approximately one week to review the 
                    <PRTPAGE P="42385"/>
                    loan's final terms before they become binding.
                </P>
                <FTNT>
                    <P>
                        <SU>64</SU>
                         12 CFR 1026.23(e).
                    </P>
                </FTNT>
                <P>
                    In 2018 the CFPB issued an RFI (2018 Inherited Rules RFI) seeking public input regarding the substance of the regulations the CFPB inherited from other Federal agencies, including whether the CFPB should issue additional rules.
                    <SU>65</SU>
                    <FTREF/>
                     A few industry commenters requested that the CFPB eliminate the right of rescission because the TRID Rule's three-day pre-consummation review period gives consumers sufficient time to review the material disclosures, and the post-consummation waiting period harms consumers refinancing into a lower interest rate loan.
                </P>
                <FTNT>
                    <P>
                        <SU>65</SU>
                         83 FR 12881 (Mar. 26, 2018).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. Reverse Mortgages</HD>
                <P>
                    Under Regulations X and Z, a reverse mortgage transaction is a nonrecourse consumer credit obligation in which a security interest is created against the consumer's principal dwelling securing one or more advances, and which is generally due and payable when the consumer dies, the dwelling is transferred, or the consumer ceases to occupy the dwelling as the principal dwelling.
                    <SU>66</SU>
                    <FTREF/>
                     Reverse mortgages are excluded from coverage of the TRID Rule.
                    <SU>67</SU>
                    <FTREF/>
                     Regulations X and Z, implementing RESPA and TILA, require creditors and settlement agents to give consumers who apply for and obtain a reverse mortgage loan different but overlapping disclosure forms regarding the loan's terms and costs.
                </P>
                <FTNT>
                    <P>
                        <SU>66</SU>
                         12 CFR 1026.33(a).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>67</SU>
                         78 FR 79730 (Dec. 31, 2013).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Overlapping Disclosure Requirements—Regulations X and Z</HD>
                <P>For closed-end reverse mortgages, TILA and Regulation Z require creditors to provide an early Truth-in-Lending (TIL) disclosure within three business days after application and at least seven business days before consummation, and before the consumer has paid a fee other than a fee for obtaining a credit report. If subsequent events make the TIL disclosure inaccurate, the creditor must provide corrected disclosures before consummation. However, if subsequent events cause the APR to exceed certain tolerances, the creditor must provide a corrected disclosure that the consumer must receive at least three business days before consummation. For open-end reverse mortgages, creditors must provide disclosures on or with an application that contains information about the creditor's open-end reverse mortgage plans. These disclosures do not include information dependent on a specific borrower's creditworthiness or value of the dwelling because these application disclosures are provided before underwriting takes place. Creditors are required to provide transaction-specific costs and terms at the time that an open-end reverse mortgage plan is opened.</P>
                <P>
                    RESPA and Regulation X also contain disclosure requirements for reverse mortgage transactions. For closed-end reverse mortgages, a lender must provide a GFE within three business days of receiving an application for a reverse mortgage.
                    <SU>68</SU>
                    <FTREF/>
                     For open-end reverse mortgages, if the TILA open-end disclosures required under 12 CFR 1026.40 are provided at the time of application, the GFE requirements are deemed to be satisfied. Lenders may not charge a fee, other than a credit report fee, prior to providing a GFE and obtaining a consumer's intent to proceed with the reverse mortgage loan. For closed-end and open-end reverse mortgage transactions, the settlement agent must permit the borrower to inspect the HUD-1 settlement statement at least one business day before closing. The GFE and HUD-1 disclosures are not tailored for reverse mortgages.
                </P>
                <FTNT>
                    <P>
                        <SU>68</SU>
                         12 CFR 1024.7.
                    </P>
                </FTNT>
                <P>In response to the 2018 Inherited Rules RFI, an industry commenter requested that the CFPB adopt a reverse-mortgage specific disclosure regime similar to the TILA-RESPA integrated disclosures created for forward mortgages.</P>
                <HD SOURCE="HD3">Total Annual Loan Cost (TALC)</HD>
                <P>Pursuant to TILA and Regulation Z, all reverse mortgage creditors must provide the TALC rate disclosure in accordance with appendix K of Regulation Z at least three business days before account opening for an open-end reverse mortgage, or consummation for a closed-end reverse mortgage. The table of TALC rates shows the estimated cost of the reverse mortgage loan, expressed as an annual rate, in nine scenarios. In order to show the effect of time and home-value appreciation on the cost of the reverse mortgage, TALC rates are based on at least three credit transaction periods (two years, a period equal to the youngest consumer's life expectancy, and a period equal to 1.4 times the youngest consumer's life expectancy); and on assumed annual house appreciation rates of 0 percent, 4 percent, and 8 percent. Generally, the longer the consumer keeps a reverse mortgage, the lower the relative cost will be because the upfront costs of the reverse mortgage will be amortized over a longer period of time. Thus, the TALC rates usually will decline over time even though the total dollar cost of the reverse mortgage is rising.</P>
                <HD SOURCE="HD3">Generic Brochures and Booklets</HD>
                <P>In addition, TILA and Regulation Z require creditors to provide mortgage applicants, including reverse mortgage applicants, with certain generic brochures or booklets. For example, in open-end transactions, creditors must provide the home equity brochure entitled “What You Should Know About Home Equity Lines of Credit” or a suitable substitute when an application for a home equity line of credit is provided to the consumer. While most closed-end reverse mortgages are fixed-rate transactions, in the rare circumstance of a closed-end adjustable rate reverse mortgage, lenders would be required to provide a booklet titled “Consumer Handbook on Adjustable Rate Mortgages” or a suitable substitute.</P>
                <HD SOURCE="HD1">II. Request for Comment</HD>
                <P>Consistent with E.O. 14393, the CFPB is considering potential regulatory changes, as appropriate and consistent with applicable law. This RFI is seeking comment from the public about some of those potential regulatory changes pertaining to (1) TILA-RESPA integrated disclosure requirements; (2) TILA rescission rights; and (3) reverse mortgages. The CFPB requests that, where possible, comments include supporting data or other information on the advantages and disadvantages of suggested regulatory changes.</P>
                <HD SOURCE="HD2">A. Timing Requirements—TRID Rule and Right of Rescission</HD>
                <P>
                    <E T="03">Question 1. Do the timing requirements materially affect consumers' ability to obtain mortgage credit? If so, in what ways and to what extent is credit availability affected?</E>
                </P>
                <P>
                    <E T="03">Question 2. Do the timing requirements increase costs for mortgage brokers, creditors, or consumers? If so, do these costs outweigh any benefits to consumers provided by such timing requirements? If so, how do these costs compare to the costs of implementing changes to the timing requirements?</E>
                </P>
                <P>
                    <E T="03">Question 3. Are there certain transaction types or specific scenarios that are inhibited or complicated by the timing requirements?</E>
                </P>
                <P>
                    <E T="03">Question 4. Are there opportunities to provide initial Loan Estimates earlier in the mortgage origination process to meet the statutorily required waiting periods while allowing consumers time to shop and reducing closing delays?</E>
                    <PRTPAGE P="42386"/>
                </P>
                <P>
                    <E T="03">Question 5. Are there ways to reduce the incidence of revised disclosures being issued while providing consumers with timely updates to settlement costs and avoiding closing delays?</E>
                </P>
                <P>
                    <E T="03">Question 6. Are there opportunities to provide Closing Disclosures earlier in the mortgage origination process to meet the statutorily required waiting periods while allowing consumers time to understand loan costs, prepare for loan consummation, and avoid closing delays?</E>
                </P>
                <P>
                    <E T="03">Question 7. What additional guidance or model forms could the CFPB issue to better facilitate consumers' decision to waive the statutorily required waiting periods for a bona fide personal financial emergency?</E>
                </P>
                <P>
                    <E T="03">Question 8. Are there any materiality-based standards that could replace or supplement timing rules, recognizing TILA's timing requirements for delivery of disclosures after application and before consummation—including issuance of a revised disclosure upon a change in APR above the prescribed tolerance? If so, how should CFPB consider defining and structuring these standards (e.g., as an optional supplement to TILA's timing requirements or a complete substitution for them)? Would these materiality-based standards result in improved administrative efficiencies while preserving or improving consumer clarity and reducing closing delays?</E>
                </P>
                <P>
                    <E T="03">Question 9. Does the three-business-day post-consummation rescission waiting period, coupled with the three-business-day pre-consummation TRID waiting period, unduly delay loan funding for refinance transactions? If so, how could the CFPB adjust the right of rescission or TRID waiting periods?</E>
                </P>
                <HD SOURCE="HD2">B. Other TRID Requirements</HD>
                <P>
                    <E T="03">Question 10. Are there adjustments to the tolerance thresholds that could improve loan execution and result in improved credit access and lower consumer costs? For example, are there instances where the CFPB should consider adjusting tolerances for transfer taxes because transfer taxes cannot be determined within three business days of application?</E>
                </P>
                <P>
                    <E T="03">Question 11. Is there additional guidance that CFPB should provide around changed circumstances, which result in the issuance of revised estimates? For example, should the CFPB consider providing additional guidance around changed circumstances in cases where a purchaser continues to negotiate with the seller for payment of charges customarily paid by the borrower?</E>
                </P>
                <P>
                    <E T="03">Question 12. Should the TRID disclosure forms be modified in a way that would improve clarity for consumers and loan execution for mortgage brokers or creditors?</E>
                </P>
                <P>
                    <E T="03">Question 13. Is there additional guidance that CFPB should provide regarding the acceptability of electronic or digital forms and signatures that would promote their use and lower costs for consumers?</E>
                </P>
                <P>
                    <E T="03">Question 14. Are there changes or clarifications to requirements specific to construction loans that would provide consumer clarity, reduce costs, or otherwise promote access to credit for the construction of residential housing? For example, should the CFPB waive certain requirements as the CFPB did when it issued a “Trial Disclosure Program Waiver Template” to the Independent Community Bankers of America (ICBA) covering the ICBA's alterative versions of the Loan Estimate and Closing Disclosure tailored to construction loans?</E>
                     
                    <SU>69</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>69</SU>
                         Consumer Fin. Prot. Bureau, 
                        <E T="03">Trial Disclosure Program Waiver Template</E>
                         (Nov. 21, 2023), 
                        <E T="03">https://files.consumerfinance.gov/f/documents/cfpb_icba-trial-disclosure-waiver_2023-11.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    <E T="03">Question 15. Are there other changes to the TRID Rule that CFPB should consider to facilitate compliance with the disclosure requirements of TILA and RESPA and to aid the consumer in understanding the transaction?</E>
                </P>
                <P>
                    <E T="03">Question 16. For any potential changes recommended regarding TRID requirements, are there any considerations for pricing or secondary market participants that CFPB should consider, such as concerns around acceptance of materiality-based standards in lieu of timing standards? For example, how would potential changes impact the pricing, liquidity, or demand for mortgages, mortgage backed securities, mortgage servicing rights, or other mortgage backed capital markets instruments?</E>
                </P>
                <HD SOURCE="HD2">C. Tailored Requirements for Small Banks and Credit Unions</HD>
                <P>
                    <E T="03">Question 17. Are there unique aspects of the loan origination process performed by small banks and credit unions for which the CFPB should consider changes to the TRID Rule specifically tailored for small banks and credit unions? If so, how should CFPB consider structuring these tailored changes (e.g., exemptions or alternative requirements)?</E>
                </P>
                <P>
                    <E T="03">Question 18. Would changes exclusive to small banks and credit unions lower costs for originators, creditors, or consumers?</E>
                </P>
                <HD SOURCE="HD2">D. Reverse Mortgages</HD>
                <P>
                    <E T="03">Question 19. The CFPB is aware that the reverse mortgage industry faces significant difficulties applying the disclosure requirements of TILA and RESPA to reverse mortgages, in light of those transactions' unusual terms and features. Would integrated and tailored reverse mortgage disclosures enable consumers to make more informed decisions?</E>
                </P>
                <P>
                    <E T="03">Question 20. Would a different set of scenario assumptions in the calculation of total annual loan cost rates in the TALC table give consumers more reasonable and accurate likely cost estimates of reverse mortgages?</E>
                </P>
                <P>
                    <E T="03">Question 21. Would a table that demonstrates how the reverse mortgage balance grows over time, using dollar amounts rather than annualized loan cost rates in the current TALC table, help consumers to better understand and evaluate the costs and the benefits of the reverse mortgage? If so, what are the important features of such a chart?</E>
                </P>
                <P>
                    <E T="03">Question 22. Would consumers benefit from a tailored disclosure informing consumers about how reverse mortgages work and about terms and risks that are important to consumers when selecting a reverse mortgage, instead of the generic brochures and booklets? If so, please provide any research or analysis of material that would be beneficial.</E>
                </P>
                <HD SOURCE="HD1">III. Regulatory Matters</HD>
                <P>The Office of Information and Regulatory Affairs within the Office of Management and Budget (OMB) has determined that this action is a “significant regulatory action” under Executive Order 12866. Accordingly, OMB has reviewed this action. The information collections contained in Regulation X, which implements RESPA, and Regulation Z, which implements TILA, are approved under the Paperwork Reduction Act by OMB and assigned Control Numbers 3170-0016 and 3170-0015 respectively. This Request for Information does not create or propose any new information collections, or, in and of itself, materially alter any existing ones.</P>
                <SIG>
                    <NAME>Russell Vought,</NAME>
                    <TITLE>Acting Director, Consumer Financial Protection Bureau.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13834 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AM-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="42387"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2026-7215; Project Identifier AD-2025-01558-T]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; The Boeing Company Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA proposes to supersede Airworthiness Directive (AD) 2023-07-09, which applies to certain The Boeing Company Model 747-400 and -8 series airplanes. AD 2023-07-09 requires inspecting for wear of the transfer pump housing inlet check valves and transfer pump motor impeller inlet adapters for the horizontal stabilizer fuel tank and doing corrective actions, if necessary, and limits the installation of affected parts. Since the FAA issued AD 2023-07-09, the manufacturer has developed further action to address the unsafe condition. This proposed AD would require repetitive inspections for damage of the transfer pump housing inlet check valves and transfer pump motor impeller inlet adapters for the horizontal stabilizer fuel tank and applicable on-condition actions. This proposed AD would also limit the installation of affected parts under certain conditions. The FAA is proposing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The FAA must receive comments on this proposed AD by August 24, 2026.</P>
                </EFFDATE>
                <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-2026-7215; 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 NPRM, 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 Boeing material identified in this proposed AD, contact Boeing Commercial Airplanes, Attention: Contractual &amp; Data Services (C&amp;DS), 2600 Westminster Blvd., MC 110-SK57, Seal Beach, CA 90740-5600; telephone 562-797-1717; website 
                        <E T="03">myboeingfleet.com.</E>
                    </P>
                    <P>
                        • You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 2200 South 216th St., Des Moines, WA. For information on the availability of this material at the FAA, call 206-231-3195. It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2026-7215.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Samuel Dorsey, Aviation Safety Engineer, FAA, 2200 South 216th St., Des Moines, WA 98198; phone: 206-231-3415; email: 
                        <E T="03">samuel.j.dorsey@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 relevant data, views, or arguments about this proposal. Send your comments using a method listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2026-7215; Project Identifier AD-2025-01558-T” at the beginning of your comments. The most helpful comments reference a specific portion of the proposal, 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 proposal 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 regulations.gov, including any personal information you provide. The agency will also post a report summarizing each substantive verbal contact received about this NPRM.</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 NPRM 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 NPRM, 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 NPRM. Submissions containing CBI should be sent to Samuel Dorsey, Aviation Safety Engineer, FAA, 2200 South 216th St., Des Moines, WA 98198; phone: 206-231-3415; email: 
                    <E T="03">samuel.j.dorsey@faa.gov.</E>
                     Any commentary that the FAA receives that 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 AD 2023-07-09, Amendment 39-22411 (88 FR 22895, April 14, 2023) (AD 2023-07-09), for certain Model 747-400 and -8 series airplanes. AD 2023-07-09 was prompted by reports of wear-through of the transfer pump motor impeller inlet adapter of the horizontal stabilizer fuel tank transfer pump caused by contact between the transfer pump housing inlet check valve and the inlet adapter. AD 2023-07-09 requires inspecting for wear of the transfer pump housing inlet check valves and transfer pump motor impeller inlet adapters for the horizontal stabilizer fuel tank and doing corrective actions, if necessary, and limits the installation of affected parts. The agency issued AD 2023-07-09 to address the development of an ignition source within the horizontal stabilizer fuel tank resulting from wear to the transfer pump housing inlet check valves and transfer pump motor impeller inlet adapters of the horizontal stabilizer fuel tank. This condition, in combination with flammable fuel vapors, could result in a fuel tank explosion and consequent loss of the airplane.</P>
                <HD SOURCE="HD1">Actions Since AD 2023-07-09 Was Issued</HD>
                <P>The preamble to AD 2023-07-09 specifies that the FAA considers that AD to be an interim action and that the FAA might consider further rulemaking if final action is identified. Since the FAA issued AD 2023-07-09, the manufacturer has developed final action to address the unsafe condition, and the FAA has determined that further rulemaking is necessary.</P>
                <P>
                    The proposed AD would replace the one-time inspections required by AD 2023-07-09 with repetitive inspections. 
                    <PRTPAGE P="42388"/>
                    The repeat intervals for these inspections are based upon analysis of reports submitted to the manufacturer following the issuance of AD 2023-07-09. Inspection of the transfer pump housing inlet check valve is proposed to be required in intervals not to exceed 20,000 flight hours. Notably different from AD 2023-07-09, the proposed AD would require an initial inspection of the transfer pump motor impeller inlet adapter within 1 year or 5,000 flight hours, whichever occurs first, and would not allow any level of wear to the inlet adapter. This inspection would be required to be repeated in intervals not to exceed 20,000 flight hours thereafter.
                </P>
                <P>The proposed AD would also remove the 0.20-inch wear allowance for the transfer pump motor impeller inlet adapter. When the FAA issued AD 2023-07-09, up to 0.20-inch of wear to the transfer pump motor impeller inlet adapter was permitted as an operational consideration due to that depth of wear being safe for the immediate future, the number of affected pumps, and the need for a short compliance time. Because of this allowance, the present level of wear across the fleet is uncertain, as some operators may have repaired pumps with any wear, while others may have returned pumps to service just below the wear limit. This, combined with uncertainty in the rate of wear progression determined from AD 2023-07-09 reports and subsequent analysis by the manufacturer, necessitate an accelerated initial inspection as specified in Boeing Alert Requirements Bulletin 747-28A2373 RB, dated November 6, 2025, for this proposed AD. Therefore, the FAA and manufacturer have reduced the initial compliance time for the transfer pump motor impeller inlet adapter inspection relative to the repeat interval. The FAA believes this initial compliance time to be practical because the transfer pumps are designed to be removed without defueling or purging the horizontal stabilizer fuel tank.</P>
                <P>Additionally, due to the need for an operationally feasible repeat interval with multiple opportunities to detect damage prior to any wear reaching a critical level, the FAA considers it necessary to remove the acceptable damage allowance previously provided under AD 2023-07-09 for transfer pump motor impeller inlet adapters, as retaining the acceptable damage allowance would require a shortened repeat interval to ensure detection of unacceptable wear prior to reaching a critical level. This action will ensure that transfer pumps installed in the horizontal stabilizer fuel tank remain at a safe level of wear between inspection opportunities.</P>
                <HD SOURCE="HD1">FAA's Determination</HD>
                <P>The FAA is issuing this NPRM after determining that the unsafe condition described previously is likely to exist or develop on other products of the same type design.</P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>
                    The FAA reviewed Boeing Alert Requirements Bulletin 747-28A2373 RB, dated November 6, 2025. This material specifies procedures for repetitive detailed inspections of the transfer pump housing inlet check valves and transfer pump motor impeller inlet adapters for any damage and applicable on-condition actions. On-condition actions include replacing the damaged transfer pump housing inlet check valve with a new or serviceable transfer pump housing inlet check valve (Option 1), or replacing the affected transfer pump housing with a transfer pump housing containing a new or serviceable transfer pump housing inlet check valve (Option 2); and replacing an affected transfer pump motor impeller with a new or serviceable transfer pump motor impeller. 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 the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <HD SOURCE="HD1">Proposed AD Requirements in This NPRM</HD>
                <P>This proposed AD would require accomplishing the actions specified in the material already described, except for any differences identified as exceptions in the regulatory text of this proposed AD. This proposed AD would also limit the installation of affected parts.</P>
                <P>
                    For information on the procedures and compliance times, see this material at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2026-7215.
                </P>
                <HD SOURCE="HD1">Interim Action</HD>
                <P>The FAA considers that this proposed AD would be an interim action. The main and center wing tanks utilize the same pump design but are currently not subject to the same unsafe condition due to the shutoff logic of the pumps. However, if further analysis or reports related to the main or center tank pumps change this assessment, the FAA might consider further rulemaking for those tanks.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD, if adopted as proposed, would affect 31 airplanes of U.S. registry. The FAA estimates the following costs to comply with this proposed AD:</P>
                <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,r50,10,r25,r25">
                    <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.
                            <LI>operators</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Inspection of transfer pump housing inlet check valve (2 per airplane)</ENT>
                        <ENT>18 work-hours × $85 per hour = $1,530 per inspection cycle</ENT>
                        <ENT>$0</ENT>
                        <ENT>$1,530 per inspection cycle</ENT>
                        <ENT>$47,430 per inspection cycle.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Inspection of transfer pump motor impeller inlet adapter (2 per airplane)</ENT>
                        <ENT>18 work-hours × $85 per hour = $1,530 per inspection cycle</ENT>
                        <ENT>0</ENT>
                        <ENT>$1,530 per inspection cycle</ENT>
                        <ENT>$47,430 per inspection cycle.</ENT>
                    </ROW>
                </GPOTABLE>
                <STARS/>
                <P>The FAA estimates the following costs to do any necessary replacements that would be required based on the results of the proposed inspection. The agency has no way of determining the number of aircraft that might need these replacements:</P>
                <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s75,r75,r25,r25">
                    <TTITLE>On-Condition Costs</TTITLE>
                    <BOXHD>
                        <CHED H="1">Action</CHED>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">Cost per product</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Replacement of transfer pump motor impeller</ENT>
                        <ENT>2 work-hours × $85 per hour = $170</ENT>
                        <ENT>Up to $2,400</ENT>
                        <ENT>$2,570.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Replacement of transfer pump housing inlet check valve (Option 1)</ENT>
                        <ENT>2 work-hours × $85 per hour = $170</ENT>
                        <ENT>$1,800</ENT>
                        <ENT>$1,970.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42389"/>
                        <ENT I="01">Replacement of transfer pump housing (Option 2)</ENT>
                        <ENT>2 work-hours × $85 per hour = $170</ENT>
                        <ENT>Up to $20,000</ENT>
                        <ENT>Up to $20,170.</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 determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify this proposed regulation:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Would not affect intrastate aviation in Alaska, and</P>
                <P>(3) Would not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 39 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>49 U.S.C. 106(g), 40113, 44701.</P>
                </AUTH>
                <SECTION>
                    <SECTNO>§ 39.13</SECTNO>
                    <SUBJECT> [Amended]</SUBJECT>
                </SECTION>
                <AMDPAR>2. The FAA amends § 39.13 by:</AMDPAR>
                <AMDPAR>a. Removing Airworthiness Directive (AD) 2023-07-09, Amendment 39-22411 (88 FR 22895, April 14, 2023), and</AMDPAR>
                <AMDPAR>b. Adding the following new AD:</AMDPAR>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="04">The Boeing Company:</E>
                         Docket No. FAA-2026-7215; Project Identifier AD-2025-01558-T.
                    </FP>
                    <HD SOURCE="HD1">(a) Comments Due Date</HD>
                    <P>The FAA must receive comments on this airworthiness directive (AD) by August 24, 2026.</P>
                    <HD SOURCE="HD1">(b) Affected ADs</HD>
                    <P>This AD replaces AD 2023-07-09, Amendment 39-22411 (88 FR 22895, April 14, 2023) (AD 2023-07-09).</P>
                    <HD SOURCE="HD1">(c) Applicability</HD>
                    <P>This AD applies to The Boeing Company Model 747-400 and -8 series airplanes, certificated in any category, as identified in Boeing Alert Requirements Bulletin 747-28A2373 RB, dated November 6, 2025.</P>
                    <HD SOURCE="HD1">(d) Subject</HD>
                    <P>Air Transport Association (ATA) of America Code 28, Fuel.</P>
                    <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                    <P>This AD was prompted by reports of wear-through of the transfer pump motor impeller inlet adapter of the horizontal stabilizer fuel tank transfer pump caused by contact between the transfer pump housing inlet check valve and the inlet adapter. The FAA is issuing this AD to address the development of an ignition source within the horizontal stabilizer fuel tank resulting from wear to the transfer pump housing inlet check valves and transfer pump motor impeller inlet adapters of the horizontal stabilizer fuel tank. The unsafe condition, if not addressed, could, in combination with flammable fuel vapors, result in a fuel tank explosion and consequent loss 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 by paragraph (h) of this AD: At the applicable times specified in the “Compliance” paragraph of Boeing Alert Requirements Bulletin 747-28A2373 RB, dated November 6, 2025, do all applicable actions identified in, and in accordance with, the Accomplishment Instructions of Boeing Alert Requirements Bulletin 747-28A2373 RB, dated November 6, 2025.</P>
                    <P>
                        <E T="04">Note 1 to paragraph (g):</E>
                         Guidance for accomplishing the actions required by this AD can be found in Boeing Alert Service Bulletin 747-28A2373, dated November 6, 2025, which is referred to in Boeing Alert Requirements Bulletin 747-28A2373 RB, dated November 6, 2025.
                    </P>
                    <HD SOURCE="HD1">(h) Exceptions to Requirements Bulletin Specifications</HD>
                    <P>Where the Compliance Time column of the tables in the “Compliance” paragraph of Boeing Alert Requirements Bulletin 747-28A2373 RB, dated November 6, 2025, refers to the original issue date of Requirements Bulletin 747-28A2373 RB, this AD requires using the effective date of this AD.</P>
                    <HD SOURCE="HD1">(i) Parts Installation Limitation</HD>
                    <P>As of the effective date of this AD, no person may install, on any airplane, a Crane Aerospace Hydro-Aire horizontal stabilizer fuel transfer pump housing, transfer pump housing inlet check valve, or transfer pump motor impeller into the horizontal stabilizer fuel tank unless the transfer pump housing inlet check valve and transfer pump motor impeller inlet adapter have been inspected as specified in paragraph (g) of this AD, as applicable, and been determined to be a serviceable part as defined in Boeing Alert Requirements Bulletin 747-28A2373 RB, dated November 6, 2025.</P>
                    <HD SOURCE="HD1">(j) Special Flight Permit</HD>
                    <P>Special flight permits may be issued in accordance with 14 CFR 21.197 and 21.199 to operate the airplane to a location where the actions required by this AD can be performed, provided the horizontal stabilizer fuel tank is defueled and both transfer pump circuit breakers are locked in the “open” position.</P>
                    <HD SOURCE="HD1">(k) 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 certification office, send it to the attention of the person identified in paragraph (l)(1) of this AD. Information may be emailed to: 
                        <E T="03">AMOC@faa.gov.</E>
                         Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the responsible Flight Standards Office.
                        <PRTPAGE P="42390"/>
                    </P>
                    <P>(2) An AMOC that provides an acceptable level of safety may be used for any repair, modification, or alteration required by this AD if it is approved by The Boeing Company Organization Designation Authorization (ODA) that has been authorized by the Manager, AIR-520, Continued Operational Safety Branch, FAA, to make those findings. To be approved, the repair method, modification deviation, or alteration deviation must meet the certification basis of the airplane, and the approval must specifically refer to this AD.</P>
                    <HD SOURCE="HD1">(l) Additional Information</HD>
                    <P>
                        (1) For more information about this AD, contact Samuel Dorsey, Aviation Safety Engineer, FAA, 2200 South 216th St., Des Moines, WA 98198; phone: 206-231-3415; email: 
                        <E T="03">samuel.j.dorsey@faa.gov.</E>
                    </P>
                    <P>(2) Material identified in this AD that is not incorporated by reference is available at the address specified in paragraph (m)(3) of this AD.</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 material listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                    <P>(2) You must use this material as applicable to do the actions required by this AD, unless the AD specifies otherwise.</P>
                    <P>(i) Boeing Alert Requirements Bulletin 747-28A2373 RB, dated November 6, 2025.</P>
                    <P>(ii) [Reserved]</P>
                    <P>
                        (3) For Boeing material identified in this AD, contact Boeing Commercial Airplanes, Attention: Contractual &amp; Data Services (C&amp;DS), 2600 Westminster Blvd., MC 110-SK57, Seal Beach, CA 90740-5600; telephone 562-797-1717; website 
                        <E T="03">myboeingfleet.com</E>
                        .
                    </P>
                    <P>(4) You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 2200 South 216th St., Des Moines, WA. For information on the availability of this material at the FAA, call 206-231-3195.</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>
                <SIG>
                    <DATED>Issued on July 7, 2026.</DATED>
                    <NAME>Brian Knaup,</NAME>
                    <TITLE>Acting Deputy Director, Integrated Certificate Management Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13869 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 71</CFR>
                <DEPDOC>[Docket No. FAA-2024-2559; Airspace Docket No. 24-AEA-11]</DEPDOC>
                <RIN>RIN 2120-AA66</RIN>
                <SUBJECT>Amendment of Class D and Class E Airspace; Morgantown, WV</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action proposes to amend the Class D and Class E airspace at Morgantown Municipal Airport-Walter L. Bill Hart Field, Morgantown, WV. The FAA is proposing this action as the result of a biennial airspace review. This action would bring the airspace into compliance with FAA orders and support instrument flight rule (IFR) procedures operations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before August 24, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send comments identified by FAA Docket No. FAA-2024-2559 and Airspace Docket No. 24-AEA-11 using any of the following methods:</P>
                    <P>
                        * 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">www.regulations.gov</E>
                         and follow the online instructions for sending your comments electronically.
                    </P>
                    <P>
                        *
                        <E T="03"> Mail:</E>
                         Send comments to Docket Operations, M-30; U.S. Department of Transportation, 1200 New Jersey Avenue SE, Room W58-213, West Building, 5th Floor, Washington, DC 20590-0001.
                    </P>
                    <P>
                        * 
                        <E T="03">Hand Delivery or Courier:</E>
                         Take comments to Docket Operations in Room W58-213 of the West Building, 5th Floor at 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>
                         Fax comments to Docket Operations at (202) 493-2251.
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         Background documents or comments received may be read at 
                        <E T="03">www.regulations.gov</E>
                         at any time. Follow the online instructions for accessing the docket or go to Docket Operations in Room W58-213 of the West Building, 5th Floor at 1200 New Jersey Avenue SE, Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        FAA Order JO 7400.11K, Airspace Designations and Reporting Points, and subsequent amendments can be viewed online at 
                        <E T="03">www.faa.gov/air_traffic/publications/.</E>
                         You may also contact the Rules and Regulations Group, Office of Policy, Federal Aviation Administration, 600 Independence Avenue SW, Washington DC 20597; telephone: (202) 267-8783.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Rebecca Shelby, Federal Aviation Administration, Operations Support Group, Central Service Center, 10101 Hillwood Parkway, Fort Worth, TX 76177; telephone (817) 222-5857.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>The FAA's authority to issue rules regarding aviation safety is found in Title 49 of the United States Code. Subtitle I, Section 106 describes the authority of the FAA Administrator. Subtitle VII, Aviation Programs, describes in more detail the scope of the agency's authority. This rulemaking is promulgated under the authority described in Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the FAA is charged with prescribing regulations to assign the use of airspace necessary to ensure the safety of aircraft and the efficient use of airspace. This regulation is within the scope of that authority as it would amend the Class D airspace, the Class E surface area airspace, the Class E airspace area designated as an extension to the Class D and Class E surface airspace, and Class E airspace extending upward from 700 feet above the surface at Morgantown Municipal Airport-Walter L. Bill Hart Field, Morgantown, WV, to support IFR operations.</P>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>The FAA invites interested persons to participate in this rulemaking by submitting written comments, data, or views. Comments are specifically invited on the overall regulatory, aeronautical, economic, environmental, and energy-related aspects of the proposal. The most helpful comments reference a specific portion of the proposal, explain the reason for any recommended change, and include supporting data. To ensure the docket does not contain duplicate comments, commenters should submit only one time if comments are filed electronically, or commenters should send only one copy of written comments if comments are filed in writing.</P>
                <P>
                    The FAA will file in the docket all comments it receives, as well as a report summarizing each substantive public contact with FAA personnel concerning this proposed rulemaking. Before acting on this proposal, the FAA will consider all comments it received on or before the closing date for comments. The FAA 
                    <PRTPAGE P="42391"/>
                    will consider comments filed after the comment period has closed if it is possible to do so without incurring expense or delay. The FAA may change this proposal in light of the comments it receives.
                </P>
                <P>
                    <E T="03">Privacy:</E>
                     In accordance with 5 U.S.C. &amp; 553(c), DOT solicits comments from the public to better inform its rulemaking process. 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-14FDMS), which can be reviewed at 
                    <E T="03">www.dot.gov/privacy.</E>
                </P>
                <HD SOURCE="HD1">Availability of Rulemaking Documents</HD>
                <P>
                    An electronic copy of this document may be downloaded through the internet at 
                    <E T="03">www.regulations.gov.</E>
                     Recently published rulemaking documents can also be accessed through the FAA's web page at 
                    <E T="03">www.faa.gov/air_traffic/publications/airspace_amendments/.</E>
                </P>
                <P>
                    You may review the public docket containing the proposal, any comments received, and any final disposition in person in the Dockets Office (see the 
                    <E T="02">ADDRESSES</E>
                     section for the address, phone number, and hours of operations). An informal docket may also be examined during normal business hours at the Federal Aviation Administration, Air Traffic Organization, Central Service Center, Operations Support Group, 10101 Hillwood Parkway, Fort Worth, TX 76177.
                </P>
                <HD SOURCE="HD1">Incorporation by Reference</HD>
                <P>
                    Class D and E airspace areas are published in paragraphs 5000, 6002, 6004, and 6005 of FAA Order JO 7400.11, Airspace Designations and Reporting Points, which is incorporated by reference in 14 CFR 71.1 on an annual basis. This document proposes to amend the current version of that order, FAA Order JO 7400.11K, dated August 4, 2025, and effective September 15, 2025. These updates would be published in the next update to FAA Order JO 7400.11. FAA Order JO 7400.11K, which lists Class A, B, C, D, and E airspace areas, air traffic service routes, and reporting points, is publicly available as listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document.
                </P>
                <HD SOURCE="HD1">The Proposal</HD>
                <P>The FAA is proposing an amendment to 14 CFR part 71 that would make the following modifications.</P>
                <P>First, the FAA proposes modifying the Class D airspace by: (1) expanding the lateral boundaries to within a 4.4-mile (increased from a 4-mile) radius of the Morgantown Municipal Airport-Walter L. Bill Hart Field, WV; and (2) replacing the term “Airport/Facility Directory” with “Chart Supplement” in the airspace legal description.</P>
                <P>Second, the FAA proposes modifying the Class E surface airspace at Morgantown Municipal Airport-Walter L. Bill Hart Field by: (1) expanding the lateral boundaries to within a 4.4-mile (increased from a 4-mile) radius of Morgantown Municipal Airport-Walter L. Bill Hart Field WV; and (2) replacing the term “Airport/Facility Directory” with “Chart Supplement”.</P>
                <P>Third, the FAA proposes amending the Class E airspace area designated as an extension to the Class D and Class E surface airspace by: (1) removing the Morgantown Very High Frequency Omnidirectional Range (VORTAC) and associated extension from the airspace legal description as they are no longer needed; (2) adding an extension beginning at the point lat 39°34′55″ N, long 79°51′57″ W, to lat 39°31′17″ N, long 79°51′13″ W, then following the 7.9-mile radius from the airport clockwise to lat 39°33′13″ N, long 80°02′31″ W, to lat 39°36′09″ N, long 79°59′46″ W, then counter clockwise following the 4.4-mile radius to the point of origination;</P>
                <P>Additionally, the FAA proposes amending the Class E5 airspace extending upward from 700 feet above the surface by expanding its lateral boundaries to within a 14.8-mile radius (increased from a 6.6-mile) radius of Morgantown Municipal Airport-Walter L. Bill Hart Field.</P>
                <P>This action is the result of an airspace review conducted as part of the decommissioning of the Morgantown VORTAC and to support IFR operations at this airport.</P>
                <HD SOURCE="HD1">Regulatory Notices and Analyses</HD>
                <P>The FAA has determined that this proposed regulation only involves an established body of technical regulations for which frequent and routine amendments are necessary to keep them operationally current. It, therefore: (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under DOT Order 2100.6B, “Rulemaking and Guidance Procedure” (March 10, 2025) and; (3) is expected to result in, at most, de minimis costs from compliance with applicable operating requirements or minor flight rerouting for operators choosing to navigate around the controlled airspace. Since this is a routine matter that will only affect air traffic procedures and air navigation, the FAA certifies that this proposed rule, when promulgated, will not have a significant economic impact on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <HD SOURCE="HD1">Environmental Review</HD>
                <P>This proposal will be subject to an environmental analysis in accordance with FAA Order 1050.1G, “FAA National Environmental Policy Act Implementing Procedures, prior to any FAA final regulatory action.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71</HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>In consideration of the foregoing, the Federal Aviation Administration proposes to amend 14 CFR part 71 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 71—DESIGNATION OF CLASS A, B, C, D, AND E AIRSPACE AREAS; AIR TRAFFIC SERVICE ROUTES; AND REPORTING POINTS</HD>
                </PART>
                <AMDPAR>1. The authority citation for 14 CFR part 71 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority: </HD>
                    <P>49 U.S.C. 106(f), 106(g); 40103, 40113, 40120; E.O. 10854, 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.</P>
                </AUTH>
                <SECTION>
                    <SECTNO>§ 71.1 </SECTNO>
                    <SUBJECT>[Amended]</SUBJECT>
                </SECTION>
                <AMDPAR>2. The incorporation by reference in 14 CFR 71.1 of FAA Order JO 7400.11K, Airspace Designations and Reporting Points, dated August 4, 2025, and effective September 15, 2025, is amended as follows:</AMDPAR>
                <EXTRACT>
                    <HD SOURCE="HD2">Paragraph 5000 Class D Airspace.</HD>
                    <STARS/>
                    <HD SOURCE="HD1">AEA WV D Morgantown, WV [Amended]</HD>
                    <FP SOURCE="FP-2">Morgantown Municipal Airport-Walter L. Bill Hart Field, WV</FP>
                    <FP SOURCE="FP1-2">(Lat 39°38′37″ N, long 79°55′03″ W)</FP>
                    <P>That airspace extending upward from the surface up to and including 3,700 feet MSL within a 4.4- mile radius of Morgantown Municipal Airport-Walter L. Bill Hart Field. This Class D airspace area is effective during the specific dates and times established in advance by a Notice to Airmen. The effective dates and times will thereafter be continuously published in the Chart Supplement.</P>
                    <STARS/>
                    <HD SOURCE="HD2">6002 Class E Airspace Areas Designated as Surface Areas.</HD>
                    <STARS/>
                    <HD SOURCE="HD1">AEA WV E2 Morgantown, WV [Amended]</HD>
                    <FP SOURCE="FP-2">Morgantown Municipal Airport-Walter L. Bill Hart Field, WV</FP>
                    <FP SOURCE="FP1-2">(Lat 39°38′37″ N, long 79°55′03″ W)</FP>
                    <P>
                        Within a 4.4-mile radius of Morgantown Municipal Airport-Walter L. Bill Hart Field. This Class E airspace area is effective during 
                        <PRTPAGE P="42392"/>
                        the specific dates and times established in advance by a Notice to Airmen. The effective dates and times will thereafter be continuously published in the Chart Supplement.
                    </P>
                    <STARS/>
                    <HD SOURCE="HD2">6004 Class E Airspace Areas Designated as an Extension to a Class D or Class E Surface Area.</HD>
                    <STARS/>
                    <HD SOURCE="HD1">AEA WV E4 Morgantown, WV [Amended]</HD>
                    <FP SOURCE="FP-2">Morgantown Municipal Airport-Walter L. Bill Hart Field, WV</FP>
                    <FP SOURCE="FP1-2">(Lat 39°38′37″ N, long 79°55′03″ W)</FP>
                    <P>That airspace extending upward from the surface within a 4.4-miles radius of the Morgantown Municipal Airport-Walter L. Bill Hart Field; and within 1.0 mile each side of the 172° bearing from the airport, beginning at the point lat 39°34′55″ N, long 79°51′57″ W, to lat 39°31′17″ N, long 79°51′13″ W, then following the 7.9-mile radius from the airport clockwise to lat 39°33′13″ N, long 80°02′31″ W, to lat 39°36′09″ N, long 79°59′46″ W, then counter clockwise following the 4.4-mile radius to the point of origination south of the airport.</P>
                    <STARS/>
                    <HD SOURCE="HD2">Paragraph 6005 Class E Airspace Areas Extending Upward From 700 Feet or More Above the Surface of the Earth.</HD>
                    <STARS/>
                    <HD SOURCE="HD1">AEA WV E5 MORGANTOWN, WV [Amended]</HD>
                    <FP SOURCE="FP-2">Morgantown Municipal Airport-Walter L. Bill Hart Field, WV</FP>
                    <FP SOURCE="FP1-2">(Lat 39°38′37″ N, long 79°55′03″ W)</FP>
                    <P>That airspace extending upward from 700 feet above the surface within a 14.8-mile radius of the Morgantown Municipal Airport-Walter L. Bill Hart Field.</P>
                    <STARS/>
                </EXTRACT>
                <SIG>
                    <DATED>Issued in Fort Worth, Texas, on June 30, 2026.</DATED>
                    <NAME>Courtney E. Johns,</NAME>
                    <TITLE>Acting Manager, Operations Support Group, ATO Central Service Center.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13861 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Drug Enforcement Administration</SUBAGY>
                <CFR>21 CFR Part 1310</CFR>
                <DEPDOC>[Docket No. DEA-1282]</DEPDOC>
                <SUBJECT>Designation of Phenethyl Halides as List I Chemicals</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Drug Enforcement Administration, Department of Justice.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Drug Enforcement Administration is proposing the control of phenethyl halides as list I chemicals under the Controlled Substances Act (CSA). Phenethyl halides are important to the illicit manufacture of fentanyl, as well as fentanyl analogues, and fentanyl-related substances as they are often used in synthetic routes to manufacture these substances. Further, in the respective synthetic routes in which they are used to manufacture fentanyl, fentanyl analogues, and fentanyl-related substances, various phenethyl halides, such as phenethyl bromide and phenethyl chloride, can be substituted for each other. If finalized, the proposed rule would subject handlers of phenethyl halides to the chemical regulatory provisions of the CSA and its implementing regulations. This proposed rulemaking does not establish a threshold for domestic and international transactions of phenethyl halides. As such, all transactions of phenethyl halides regardless of size or concentration, shall be regulated and would be subject to control under the CSA.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted electronically or postmarked on or before August 10, 2026. Commenters should be aware that the electronic Federal Docket Management System will not accept any comments after 11:59 p.m. Eastern Time on the last day of the comment period.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>To ensure proper handling of comments, please reference “Docket No. DEA-1282” on all electronic and written correspondence, including any attachments.</P>
                    <P>
                        • 
                        <E T="03">Electronic comments:</E>
                         The Drug Enforcement Administration (DEA) encourages that all comments be submitted electronically through the Federal eRulemaking Portal, which provides the ability to type short comments directly into the comment field on the web page or attach a file for lengthier comments. Please go to 
                        <E T="03">https://www.regulations.gov</E>
                         and follow the online instructions at that site for submitting comments. Upon completion of your comment submission, you will receive a Comment Tracking Number. Please be aware that submitted comments are not instantaneously available for public view on 
                        <E T="03">Regulations.gov.</E>
                         If you have received a Comment Tracking Number, your comment has been successfully submitted and there is no need to resubmit the same comment.
                    </P>
                    <P>
                        • 
                        <E T="03">Paper comments:</E>
                         Paper comments that duplicate electronic submissions are not necessary. Should you wish to mail a paper comment, 
                        <E T="03">in lieu of</E>
                         an electronic comment, it should be sent via regular or express mail to: Drug Enforcement Administration, Attn: DEA 
                        <E T="04">Federal Register</E>
                         Representative/DPW, 8701 Morrissette Drive, Springfield, Virginia 22152.
                    </P>
                    <P>
                        • 
                        <E T="03">Paperwork Reduction Act Comments:</E>
                         All comments concerning collections of information under the Paperwork Reduction Act must be submitted to the Office of Information and Regulatory Affairs, OMB, Attention: Desk Officer for DOJ, Washington, DC 20503. Please state that your comment refers to Docket No. DEA-1282.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dr. Terrence L. Boos, Drug and Chemical Evaluation Section, Diversion Control Division, Drug Enforcement Administration; Telephone: (571) 362-3249.</P>
                    <P>
                        As required by 5 U.S.C. 553(b)(4), a summary of this proposed rule may be found in the docket for this rulemaking at 
                        <E T="03">www.regulations.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Posting of Public Comments</HD>
                <P>
                    All comments received in response to this docket are considered part of the public record. The Drug Enforcement Administration (DEA) will make comments available for public inspection online at 
                    <E T="03">https://www.regulations.gov,</E>
                     unless reasonable cause is given. Such information includes personal or business identifying information (such as name, address, State or Federal identifiers, etc.) voluntarily submitted by the commenter.
                </P>
                <P>
                    Commenters submitting comments which include personal identifying information (PII), confidential, or proprietary business information that the commenter does not want made publicly available should submit two copies of the comment. One copy must be marked “CONTAINS CONFIDENTIAL INFORMATION” and should clearly identify all PII or business information the commenter does not want to be made publicly available, including any supplemental materials. DEA will review this copy, including the claimed PII and confidential business information, in its consideration of comments. The second copy should be marked “TO BE PUBLICLY POSTED” and must have all claimed PII and business information already redacted. DEA will post only the redacted comment on 
                    <E T="03">https://www.regulations.gov</E>
                     for public inspection. DEA generally will not redact additional information contained in the comment marked “TO BE PUBLICLY POSTED.” The Freedom of Information Act applies to all comments received.
                </P>
                <P>
                    For easy reference, an electronic copy of this document and a plain language 
                    <PRTPAGE P="42393"/>
                    summary of this notice of proposed rulemaking are available at 
                    <E T="03">https://www.regulations.gov.</E>
                </P>
                <HD SOURCE="HD1">Legal Authority</HD>
                <P>
                    The Controlled Substances Act (CSA) authorizes the Attorney General to specify, by regulation, chemicals as list I chemicals.
                    <SU>1</SU>
                    <FTREF/>
                     The Attorney General has delegated her authority to designate list I chemicals to the Administrator of DEA (Administrator).
                    <SU>2</SU>
                    <FTREF/>
                     A “list I chemical” is defined as “a chemical that is used in manufacturing a controlled substance in violation of [the CSA] and is important to the manufacture of the controlled substances.” 
                    <SU>3</SU>
                    <FTREF/>
                     The current list of all listed chemicals is published at 21 CFR 1310.02. DEA regulations set forth the process by which DEA may add a chemical as a listed chemical. As set forth in 21 CFR 1310.02(c), the agency may do so by publishing a final rule in the 
                    <E T="04">Federal Register</E>
                     following a published notice of proposed rulemaking with at least 30 days for public comments.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         21 U.S.C. 802(34).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         28 CFR 0.100(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         21 U.S.C. 802(34).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The clandestine manufacture of fentanyl, fentanyl analogues, and fentanyl-related substances remains extremely concerning as the distribution of these substances continue to drive drug-related overdose deaths in the United States. Fentanyl is a synthetic opioid and was first synthesized in Belgium in the late 1950s. Fentanyl was introduced into medical practice and is approved for medical practitioners in the United States to prescribe lawfully for anesthesia and analgesia. However, due to its desirable pharmacological effects, fentanyl can be used outside of its approved medical purposes. Opioid dependent individuals can use fentanyl as a substitute for heroin, oxycodone, or other opioids. Therefore, though fentanyl has an accepted medical use in the Unites States, it is controlled as a schedule II controlled substance due to its high potential for abuse.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         21 U.S.C. 812(c) Schedule II(b)(6); 21 CFR 1308.12(c)(9). On July 16, 2025, Congress enacted the HALT Fentanyl Act, Public Law 119-26, which, among other things, permanently places fentanyl-related substances as a class into schedule I of the CSA.
                    </P>
                </FTNT>
                <P>
                    Moreover, there are a substantial number of fentanyl analogues 
                    <SU>5</SU>
                    <FTREF/>
                     and fentanyl-related substances 
                    <SU>6</SU>
                    <FTREF/>
                     that are being distributed on the illicit drug market despite DEA's recent actions placing them under control of the CSA as schedule I controlled substances.
                    <SU>7</SU>
                    <FTREF/>
                     Illicit manufacturers of fentanyl, fentanyl analogues, and fentanyl-related substances attempt to utilize unregulated precursor chemicals to evade law enforcement detection and precursor chemical controls in order to manufacture these substances. This strategy allows for the synthesis of a variety of fentanyl analogues and fentanyl-related substances by making slight modifications to the core fentanyl structure while maintaining the same synthetic methodology used to synthesize fentanyl, fentanyl analogues, and fentanyl-related substances.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Schedules of Controlled Substances: Temporary Placement of Seven Fentanyl-Related Substances in Schedule I. 83 FR 4580 (Feb. 1, 2018).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Schedules of Controlled Substances: Temporary Placement of Fentanyl-Related Substances in Schedule I, 83 FR 5188 (Feb. 6, 2018).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Schedules of Controlled Substances: Placement of 10 Specific Fentanyl-Related Substances in Schedule I, 86 FR 22113 (Apr. 27, 2021).
                    </P>
                </FTNT>
                <P>
                    The unlawful trafficking of fentanyl, fentanyl analogues, and fentanyl-related substances in the United States continues to pose an imminent hazard to public safety. Since 2012, fentanyl has shown a dramatic increase in the illicit drug supply as a single substance, in mixtures with other illicit drugs (
                    <E T="03">e.g.,</E>
                     heroin, cocaine, and methamphetamine), and in forms that mimic pharmaceutical preparations including prescription opiates and benzodiazepines.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         United Nations Office on Drugs and Crime, Global SMART Update Volume 17, March 2017. 
                        <E T="03">https://www.unodc.org/documents/scientific/Global_SMART_Update_17_web.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    DEA has noted a significant increase in overdoses and overdose fatalities from fentanyl, fentanyl analogues, and fentanyl-related substances in the United States in recent years. According to the Centers for Disease Control and Prevention (CDC), opioids, mainly synthetic opioids (which includes fentanyl), are predominantly responsible for drug overdose deaths in recent years. According to CDC WONDER,
                    <SU>9</SU>
                    <FTREF/>
                     drug-induced overdose deaths involving synthetic opioids (excluding methadone) in the United States increased from 36,359 in 2019, to 56,516 in 2020, to 70,601 in 2021, and to 73,838 in 2022, with only a slight decrease to 72,776 in 2023, and a further decrease to 47,735 in 2024. Based on provisional data, the predicted number of drug overdose deaths involving synthetic opioids (excluding methadone) in the United States for the 12 months ending October 2025 is 39,649 individuals, or approximately 55.4 percent of all drug-induced overdose deaths for that time period.
                    <SU>10</SU>
                    <FTREF/>
                     Overdose fatalities involving synthetic opioids coincides with a dramatic increase in law enforcement encounters of fentanyl, fentanyl analogues, and fentanyl-related substances. According to the National Forensic Laboratory Information System (NFLIS-Drug),
                    <SU>11</SU>
                    <FTREF/>
                     reports from forensic laboratories of drug items containing fentanyl, fentanyl analogues, and fentanyl-related substances increased dramatically since 2016, as shown in Table 1 (*2025 data still being reported).
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Centers for Disease Control and Prevention, National Center for Health Statistics. National Vital Statistics System, Provisional Mortality on CDC WONDER Online Database. Data are from the final Multiple Cause of Death Files, 2018-2024, and from provisional data for years 2025 and later, as compiled from data provided by the 57 vital statistics jurisdictions through the Vital Statistics Cooperative Program. Accessed at 
                        <E T="03">http://wonder.cdc.gov/mcd-icd10-provisional.html</E>
                         on March 18, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Ahmad FB, Cisewski JA, Rossen LM, Sutton P. Provisional drug overdose death counts. National Center for Health Statistics. 2026. Accessed at 
                        <E T="03">https://www.cdc.gov/nchs/nvss/vsrr/drug-overdose-data.htm</E>
                         on March 18, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         The National Forensic Laboratory Information System (NFLIS-Drug) is a national forensic laboratory reporting system that systematically collects results from drug chemistry analyses conducted by Federal, State and local forensic laboratories in the United States. While NFLIS-Drug data is not direct evidence of abuse, it can lead to an inference that a drug has been diverted and abused. See 76 FR 77330, 77332 (December 12, 2011). NFLIS-Drug data was queried on January 8, 2026; *2025 data is still reporting.
                    </P>
                </FTNT>
                <GPOTABLE COLS="11" OPTS="L2,nj,i1" CDEF="s50,6,6,6,8,8,8,8,8,8,6">
                    <TTITLE>Table 1—Annual Reports of Fentanyl and Select Fentanyl Analogues and Fentanyl-Related Substances Identified in Drug Encounters</TTITLE>
                    <BOXHD>
                        <CHED H="1">Year</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">2023</CHED>
                        <CHED H="1">2024</CHED>
                        <CHED H="1">* 2025</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Annual Fentanyl Reports</ENT>
                        <ENT>37,158</ENT>
                        <ENT>61,648</ENT>
                        <ENT>90,014</ENT>
                        <ENT>108,225</ENT>
                        <ENT>126,404</ENT>
                        <ENT>166,651</ENT>
                        <ENT>177,227</ENT>
                        <ENT>183,009</ENT>
                        <ENT>154,015</ENT>
                        <ENT>89,003</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Annual Reports of select fentanyl analogues and fentanyl-related substances</ENT>
                        <ENT>7,624</ENT>
                        <ENT>22,072</ENT>
                        <ENT>16,121</ENT>
                        <ENT>20,932</ENT>
                        <ENT>8,005</ENT>
                        <ENT>26,691</ENT>
                        <ENT>30,978</ENT>
                        <ENT>21,511</ENT>
                        <ENT>19,000</ENT>
                        <ENT>7.616</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="42394"/>
                <HD SOURCE="HD1">Role of Phenethyl Halides in the Synthesis of Fentanyl</HD>
                <P>
                    Fentanyl, fentanyl analogues, and fentanyl-related substances are not naturally occurring substances. As such, these substances can only be manufactured through synthetic organic chemistry. Synthetic organic chemistry is the process in which a new organic molecule is created through a series of chemical reactions, which involve precursor chemicals. Through chemical reactions using precursor chemicals, chemical structures can be modified in a desired fashion. These chemical reaction sequences, also known as synthetic pathways, are designed to create a desired substance. Several synthetic pathways to fentanyl, fentanyl analogues, and fentanyl-related substances have been identified in clandestine laboratory settings; these include the original “Janssen method,” the “Siegfried method,” and the “Gupta method.” In response to the illicit manufacture of fentanyl, fentanyl analogues, and fentanyl-related substances using these methods, DEA controlled 
                    <E T="03">N</E>
                    -phenethyl-4-piperidone (NPP),
                    <FTREF/>
                    <SU>12</SU>
                      
                    <E T="03">N</E>
                    -(1-benzylpiperidin-4-yl)-
                    <E T="03">N</E>
                    -phenylpropionamide (benzylfentanyl), 
                    <E T="03">N</E>
                    -phenylpiperidin-4-amine (4-anilinopiperidine; including its amides and carbamates),
                    <SU>13</SU>
                    <FTREF/>
                     and 4-piperidone (piperidin-4-one) 
                    <SU>14</SU>
                    <FTREF/>
                     as list I chemicals, and 4-anilino-
                    <E T="03">N</E>
                    -phenethylpiperidine (ANPP) 
                    <SU>15</SU>
                    <FTREF/>
                     and 
                    <E T="03">N</E>
                    -phenyl-
                    <E T="03">N</E>
                    -(piperidin-4-yl)propionamide (norfentanyl) 
                    <SU>16</SU>
                    <FTREF/>
                     as schedule II immediate precursors under the CSA.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         Control of a Chemical Precursor Used in the Illicit Manufacture of Fentanyl as a List I Chemical, 72 FR 20039 (Apr. 23, 2007).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         Designation of Benzylfentanyl and 4-Anilinopiperidine, Precursor Chemicals Used in the Illicit Manufacture of Fentanyl, as List I Chemicals, 85 FR 20822 (Apr. 15, 2020).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         Designation of 4-Piperidone as a List I Chemical, 88 FR 21902 (Apr. 12, 2023).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         Control of Immediate Precursor Used in the Illicit Manufacture of Fentanyl as a Schedule II Controlled Substance, 75 FR 37295 (June 29, 2010).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Control of the Immediate Precursor Norfentanyl Used in the Illicit Manufacture of Fentanyl as a Schedule II Controlled Substance, 85 FR 21320 (Apr. 17, 2020).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Phenethyl Halides</HD>
                <P>
                    Phenethyl halides serve as precursors in the synthesis of fentanyl, its analogues, and fentanyl-related substances. Various phenethyl halides have been documented in the scientific literature and in reported clandestine seizures. Examples of these include phenethyl bromide and phenethyl chloride. The original published synthetic pathway to fentanyl, known as the Janssen method, involves the list I chemical benzylfentanyl 
                    <SU>17</SU>
                    <FTREF/>
                     and schedule II immediate precursor norfentanyl.
                    <SU>18</SU>
                    <FTREF/>
                     In this synthetic route, benzylfentanyl is converted to norfentanyl. Norfentanyl is reacted with phenethyl chloride (also known as 2-chloroethyl benzene) to complete the synthesis of fentanyl. This synthetic route can also be easily modified to produce fentanyl analogues and fentanyl-related substances.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         Designation of Benzylfentanyl and 4-Anilinopiperidine, Precursor Chemicals Used in the Illicit Manufacture of Fentanyl, as List I Chemicals, 85 FR 20822 (April 15, 2020).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         Control of the Immediate Precursor Norfentanyl Used in the Illicit Manufacture of Fentanyl as a Schedule II Controlled Substance, 85 FR 21320 (April 17, 2020).
                    </P>
                </FTNT>
                <P>
                    In the Siegfried method, phenethyl bromide (also known as 2-bromoethyl benzene) is reacted with 4-piperidone, a list I chemical under the CSA, to produce NPP, another list I chemical, which is further converted to ANPP,
                    <SU>19</SU>
                    <FTREF/>
                     the schedule II immediate precursor in the production of fentanyl using this method. One additional step completes the synthesis of fentanyl. This synthetic route can also be easily modified to produce fentanyl analogues and fentanyl-related substances.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         Control of Immediate Precursor Used in the Illicit Manufacture of Fentanyl as a Schedule II Controlled Substance, 75 FR 37295 (June 29, 2010).
                    </P>
                </FTNT>
                <P>
                    In addition to the Janssen and Siegfried methods, clandestine manufacturers are using other methods to synthesize fentanyl, one of which is known as the Gupta method. In this synthetic route, 4-piperidone is used to synthesize 4-anilinopiperidine, another list I chemical under the CSA,
                    <SU>20</SU>
                    <FTREF/>
                     which serves as an alternative to NPP for the synthesis of ANPP, albeit through a different synthetic route. 4-Anilinopiperidine is reacted with phenethyl bromide to produce ANPP, which is then converted to the schedule II controlled substance fentanyl. This synthetic route can also be easily modified to produce fentanyl analogues and fentanyl-related substances.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         Designation of Benzylfentanyl and 4-Anilinopiperidine, Precursor Chemicals Used in the Illicit Manufacture of Fentanyl, as List I Chemicals, 85 FR 20822 (April 15, 2020).
                    </P>
                </FTNT>
                <P>
                    Phenethyl halides are attractive to illicit manufacturers due to the lack of regulations on these chemicals; they are readily available from chemical suppliers. Additionally, these substances, (
                    <E T="03">i.e.,</E>
                     phenethyl fluoride, phenethyl chloride, phenethyl bromide, phenethyl iodide) are closely related and may be substituted for each other in many of the known synthetic routes. These synthetic routes can be easily used, and modified, in the illicit manufacture of fentanyl, fentanyl analogues, and fentanyl-related substances.
                </P>
                <HD SOURCE="HD1">Information Gathered by DEA Concerning Phenethyl Halides</HD>
                <P>
                    On October 28, 2024, DEA published in the 
                    <E T="04">Federal Register</E>
                     an Advance Notice of Proposed Rulemaking (ANPRM) 
                    <SU>21</SU>
                    <FTREF/>
                     in anticipation of proposing to designate phenethyl bromide, and related halides and sulfonates as list I chemicals. The ANPRM invited interested persons to submit information related to current uses of phenethyl bromide, and related halides and sulfonates (other than for the synthesis of fentanyl), in order to properly determine the effect such a proposed action would have on legitimate industry.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Possible Control of Phenethyl Bromide as a List I Chemical, 89 FR 85459 (Oct. 24, 2024).
                    </P>
                </FTNT>
                <P>DEA solicited input from all potentially affected parties regarding: (1) the types of legitimate industries using phenethyl bromide, and related halides and sulfonates; (2) the legitimate uses, legitimate needs, and quantities produced, used, and distributed of phenethyl bromide, and related halides and sulfonates; (3) the size of the domestic market for phenethyl bromide, and related halides and sulfonates, if any; (4) the number of manufacturers of phenethyl bromide, and related halides and sulfonates; (5) the number of distributors of phenethyl bromide, and related halides and sulfonates; (6) the level of import and export of phenethyl bromide, and related halides and sulfonates; (7) the potential burden that controlling phenethyl bromide, and related halides and sulfonates, as a list I chemical may have on any legitimate industry and trade; (8) the potential number of individuals/firms that may be adversely affected by such regulatory controls (particularly with respect to the impact on small businesses); and (9) any other information on the manner of manufacturing, distribution, consumption, storage, disposal, and uses of phenethyl bromide, and related halides and sulfonates, by industry and others. DEA invited all interested parties to provide any information on any legitimate uses of phenethyl bromide, and related halides and sulfonates, in industry, commerce, academia, research and development, or other applications. DEA sought both quantitative and qualitative data.</P>
                <HD SOURCE="HD1">Comments</HD>
                <P>
                    DEA received three responses to the ANPRM. The comments stated support for, and against, the control of 
                    <PRTPAGE P="42395"/>
                    phenethyl bromide and/or related substances.
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One comment was in support of the control of phenethyl bromide and other phenethyl halides but was vigorously opposed to the control of phenethyl sulfonates. The comment stated that it was unaware of other uses in industry except to synthesize fentanyl and other phenethyl-amides.
                </P>
                <P>
                    <E T="03">DEA Response:</E>
                     DEA agrees with the comment to control phenethyl bromide and other phenethyl halides. The opposition stated in this comment to the control of phenethyl sulfonates is outside the scope of this proposed rule as those substances are not being proposed for control.
                </P>
                <P>
                    <E T="03">Comment:</E>
                     The second comment was against the control of phenethyl bromide due to its importance in the synthesis of certain medications and study of new therapeutic compounds. The comment also noted the versatility of phenethyl bromide in a number of legitimate scientific and industrial applications. It further argued that overregulating individual chemicals fails to address the broader strategies employed by illicit manufacturers.
                </P>
                <P>
                    <E T="03">DEA Response:</E>
                     DEA appreciates the commenter's concern for the use of these chemicals in the synthesis of certain medications and study of new therapeutic compounds and application in scientific and industrial applications. DEA is aware that phenethyl halides may be used as an intermediate in several processes, including, but not limited to, pharmaceutical (including fentanyl manufacturing), scientific, and industrial applications. Designating phenethyl halides as list I chemicals does not preclude the use of phenethyl halides for end users (
                    <E T="03">i.e.,</E>
                     those using them as an intermediate chemical or in chemical synthesis). DEA registration for list I chemicals is only for those who are manufacturing, distributing, importing, or exporting list I chemicals. It is not required for those doing synthesis, unless they are also participating in one of the aforementioned activities that require registration. Therefore, unless the user is also manufacturing, distributing, importing, or exporting phenethyl halides, the proposed action will not affect industries that may be using phenethyl halides as an intermediate in synthesis. Any potential burdens on industry are outweighed by the public health and public safety benefits of listing phenethyl halides.
                </P>
                <P>With regard to the portion of the comment stating that overregulating individual chemicals fails to address the broader strategies employed by illicit manufacturers, DEA is concerned with the abuse of illicitly manufactured fentanyl in the United States and believes this rule will help control the illicit manufacture of fentanyl.</P>
                <P>
                    <E T="03">Comment:</E>
                     The third comment was in favor of regulating phenethyl bromide if it meets the requirements, and it also recommended regulating the online sales of this substance to mitigate access and distribution and prevent further manufacturing of fentanyl and fentanyl analogous substances.
                </P>
                <P>
                    <E T="03">DEA Response:</E>
                     DEA agrees with the comment favoring regulation of phenethyl bromide. With regard to the recommendation to regulate online sales to mitigate access and distribution and prevent further manufacturing of fentanyl and fentanyl analogous substances, the proposed rule, if finalized, will regulate, in addition to manufacturing, the distribution, import, and export of phenethyl halides. As such, DEA believes the proposed controls will help mitigate the access and illegal distribution of these substances to manufacture fentanyl and analogous substances.
                </P>
                <HD SOURCE="HD1">Proposed Designation of Phenethyl Halides as List I Chemicals</HD>
                <P>The CSA, specifically 21 U.S.C. 802(34), and its implementing regulations at 21 CFR 1310.02(c), provide the Attorney General with the authority to specify, by regulation, additional precursor or essential chemicals as listed chemicals if they are used in the manufacture of controlled substances in violation of the CSA. Recent law enforcement encounters indicate phenethyl halides are being used in the illicit manufacture of the schedule II controlled substance fentanyl. This proposed rule would regulate phenethyl halides as list I chemicals because DEA finds that phenethyl halides are used in the illicit manufacture of the controlled substance fentanyl, fentanyl analogues, and fentanyl related substances and are important to the manufacture of these substances because they can be used, and substituted for each other, in various synthetic pathways which are used in the illicit manufacture of fentanyl, fentanyl analogues, and fentanyl related substances.</P>
                <HD SOURCE="HD1">Chemical Mixtures of Phenethyl Halides</HD>
                <P>This rulemaking also proposes that chemical mixtures containing phenethyl halides would not be exempt from regulatory requirements at any concentration, unless a manufacturer submits to DEA an application for exemption of such chemical mixture, DEA accepts the application for filing, and DEA exempts the chemical mixture in accordance with 21 CFR 1310.13 (exemption of chemical mixtures by application). The control of chemical mixtures containing any amount of phenethyl halides is necessary to prevent the extraction, isolation, and use of phenethyl halides in the illicit manufacture of fentanyl, fentanyl analogues, and fentanyl related substances. This rule proposes the modification of the “Table of Concentration Limits” in 21 CFR 1310.12(c) to reflect the fact that chemical mixtures containing any amount of phenethyl halides are subject to CSA chemical control provisions.</P>
                <HD SOURCE="HD1">Application Process for Exemption of Chemical Mixtures</HD>
                <P>
                    DEA has implemented an application process to exempt mixtures from the requirements of the CSA and its implementing regulations.
                    <SU>22</SU>
                    <FTREF/>
                     Manufacturers may apply for an automatic exemption for those mixtures that do not meet the criteria set forth in 21 CFR 1310.12(d). Pursuant to 21 CFR 1310.13(a), DEA may grant an exemption of a chemical mixture, by publishing a final rule in the 
                    <E T="04">Federal Register,</E>
                     if DEA determines that: (1) the mixture is formulated in such a way that it cannot be easily used in the illicit production of a controlled substance, and (2) the listed chemical or chemicals cannot be readily recovered.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         21 CFR 1310.13 specifies that this chemical mixture is a chemical mixture consisting of two or more chemical components, at least one of which is a list I or list II chemical. 
                        <E T="03">See also</E>
                         21 CFR 1300.02 (defining the term “chemical mixture”).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Requirements for Handling List I Chemicals</HD>
                <P>If finalized as proposed, the designation of phenethyl halides as list I chemicals would subject handlers (manufacturers, distributors, importers, and exporters) and proposed handlers to all of the regulatory controls and administrative, civil, and criminal sanctions applicable to the manufacture, distribution, importing, and exporting of list I chemicals. Upon publication of a final rule, persons potentially handling phenethyl halides, including regulated chemical mixtures containing phenethyl halides, would be required to comply with list I chemical regulations, including the following:</P>
                <P>
                    1. 
                    <E T="03">Registration.</E>
                     Any person who handles (manufactures, distributes, imports, or exports), or proposes to engage in such handling of, phenethyl halides, including chemical mixtures containing phenethyl halides, or proposes to engage in the manufacture, 
                    <PRTPAGE P="42396"/>
                    distribution, importation, or exportation of phenethyl halides, including chemical mixtures containing phenethyl halides, must obtain a registration pursuant to 21 U.S.C. 822, 823, 957, and 958. Regulations describing registration for list I chemical handlers are set forth in 21 CFR part 1309. DEA regulations require separate registrations for manufacturing, distributing, importing, and exporting of list I chemicals.
                    <SU>23</SU>
                    <FTREF/>
                     Further, a separate registration is required for each principal place of business at one general physical location where list I chemicals are manufactured, distributed, imported, or exported by a person.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         21 CFR 1309.21.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         21 U.S.C. 822(e)(1) (separate registration requirements pertaining to manufacturing or distributing a list I chemical); 21 CFR 1309.23(a).
                    </P>
                </FTNT>
                <P>
                    DEA notes that under the CSA, “warehousemen” are not required to register and may lawfully possess list I chemicals, if the possession of those chemicals is in the usual course of business or employment. Under DEA implementing regulations, the warehouse in question must receive the list I chemical from a DEA registrant and shall only distribute the list I chemical back to the DEA registrant and registered location from which it was received.
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         See 21 CFR 1309.23(b)(1).
                    </P>
                </FTNT>
                <P>A warehouse that distributes list I chemicals to persons other than the registrant and registered location from which they were obtained is conducting distribution activities and is required to register as such.</P>
                <P>Upon publication of a final rule, any person manufacturing, distributing, importing, or exporting phenethyl halides or a chemical mixture containing phenethyl halides would become subject to the registration requirement under the CSA. DEA recognizes, however, that it is not possible for persons who are subject to the registration requirements to immediately complete and submit an application for registration, and for DEA to immediately issue registrations for those activities. Therefore, to allow any continued legitimate commerce in phenethyl halides or a chemical mixture containing phenethyl halides, DEA is proposing to establish in 21 CFR 1310.09, a temporary exemption from the registration requirement for persons desiring to engage in activities with phenethyl halides or a chemical mixture containing phenethyl halides, provided that DEA receives a properly completed application for registration or application for exemption of a chemical mixture under 21 CFR 1310.13 on or before 30 days after publication of a final rule implementing regulations regarding phenethyl halides. The temporary exemption for such persons will remain in effect until DEA takes final action on their application for registration or application for exemption of a chemical mixture.</P>
                <P>The temporary exemption applies solely to the registration requirement; all other chemical control requirements, including recordkeeping and reporting, would become effective on the effective date of the final rule. This is necessary because a delay in regulating these transactions could result in increased diversion of chemicals desirable to drug traffickers.</P>
                <P>Additionally, the temporary exemption for registration does not suspend applicable federal criminal laws relating to phenethyl halides, nor does it supersede State or local laws or regulations. All handlers of phenethyl halides must comply with applicable State and local requirements in addition to the CSA regulatory controls.</P>
                <P>
                    2. 
                    <E T="03">Records and Reports.</E>
                     Every DEA registrant would be required to maintain records and submit reports with respect to phenethyl halides pursuant to 21 U.S.C. 830 and in accordance with 21 CFR 1310.04 and 1310.05. Pursuant to 21 CFR 1310.04, a record must be kept for two years after the date of a transaction involving a listed chemical, provided the transaction is a regulated transaction.
                </P>
                <P>
                    Each regulated bulk manufacturer of a listed chemical will be required to submit manufacturing, inventory, and use data on an annual basis.
                    <SU>26</SU>
                    <FTREF/>
                     Existing standard industry reports containing the required information are acceptable, provided the information is separate or readily retrievable from the report.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         21 CFR 1310.05(d).
                    </P>
                </FTNT>
                <P>
                    The CSA and its implementing regulations require that each regulated person must report to DEA any regulated transaction involving an extraordinary quantity of a listed chemical, an uncommon method of payment or delivery, or any other circumstance that the regulated person believes may indicate that the listed chemical will be used in violation of subchapter I of the CSA. In addition, regulated persons must report any proposed regulated transaction with a person whose description or other identifying characteristics DEA has previously furnished to the regulated person, any unusual or excessive loss or disappearance of a listed chemical under the control of the regulated person, and any in-transit loss in which the regulated person is the supplier.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         21 U.S.C. 830(b); 21 CFR 1310.05(a) and (b).
                    </P>
                </FTNT>
                <P>
                    3. 
                    <E T="03">Importation and Exportation.</E>
                     All importation and exportation of phenethyl halides or a chemical mixture containing phenethyl halides would need to comply with 21 U.S.C. 957, 958, and 971 and in accordance with 21 CFR part 1313.
                </P>
                <P>
                    4. 
                    <E T="03">Security.</E>
                     All applicants and registrants would be required to provide effective controls against theft and diversion of list I chemicals in accordance with 21 CFR 1309.71-1309.73.
                </P>
                <P>
                    5. 
                    <E T="03">Administrative Inspection.</E>
                     Places, including factories, warehouses, or other establishments and conveyances, where registrants or other regulated persons may lawfully hold, manufacture, distribute, or otherwise dispose of a list I chemical or where records relating to those activities are maintained, are controlled premises as defined in 21 U.S.C. 880(a) and 21 CFR 1316.02(c). The CSA allows for administrative inspections of these controlled premises as provided in 21 CFR part 1316, subpart A.
                    <SU>28</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         21 U.S.C. 880.
                    </P>
                </FTNT>
                <P>
                    6. 
                    <E T="03">Liability.</E>
                     Any activity involving phenethyl halides not authorized by, or in violation of, the CSA, would be unlawful, and would subject the person to administrative, civil, and/or criminal action.
                </P>
                <HD SOURCE="HD1">Regulatory Analyses</HD>
                <HD SOURCE="HD2">Executive Orders 12866, 13563, 14192, and 14294 (Regulatory Review)</HD>
                <P>DEA has determined that this rulemaking is not a “significant regulatory action” under section 3(f) of Executive Order (E.O.) 12866, Regulatory Planning and Review. Accordingly, this proposed rule has not been submitted to the Office of Management and Budget for review. This proposed rule has been drafted and reviewed in accordance with E.O. 12866, “Regulatory Planning and Review,” section 1(b), Principles of Regulation and E.O. 13563, “Improving Regulation and Regulatory Review,” section 1(b), General Principles of Regulation.” DEA scheduling actions are not subject to either E.O. 14192, Unleashing Prosperity Through Deregulation, or E.O. 14294, Fighting Overcriminalization in Federal Regulations.</P>
                <P>
                    DEA is proposing the control of phenethyl halides as list I chemicals under the CSA. DEA finds that phenethyl halides are used in and important to the illicit manufacture of 
                    <PRTPAGE P="42397"/>
                    the controlled substances fentanyl, fentanyl analogues, and fentanyl-related substances. Phenethyl halides may be used as replacements for each other in various synthetic pathways to make fentanyl, its analogues, and related substances. If finalized, the proposed rule would subject handlers of phenethyl halides to the chemical regulatory provisions of the CSA and its implementing regulations. This proposed rulemaking does not establish a threshold for domestic and international transactions of phenethyl halides. As such, all transactions of phenethyl halides, regardless of size, shall be regulated. In addition, chemical mixtures containing phenethyl halides are not exempt from regulatory requirements at any concentration. Therefore, all transactions of chemical mixtures containing any quantity of phenethyl halides shall be regulated pursuant to the CSA. If finalized as proposed, phenethyl halides will be subject to all of the regulatory control and administrative, civil, and criminal sanctions applicable to the manufacture, distribution, importing, and exporting of list I chemicals.
                </P>
                <P>Phenethyl halides are used for the legitimate manufacturing of pharmaceutical fentanyl as well as clandestinely synthesized illicit fentanyl. DEA has searched information in the public domain for legitimate uses of phenethyl halides and has documented that phenethyl halides may be used as an intermediary chemical in several industries, including the production of fentanyl. Any manufacturer, distributor, importer, or exporter of phenethyl halides for the production of legitimate pharmaceutical fentanyl who are not already registered with DEA, if they exist at all, would incur costs if this proposed rule is finalized. Entities who currently use phenethyl halides for the legitimate manufacturing of pharmaceutical fentanyl should be registered with DEA. DEA welcomes any comments related to the uses of phenethyl halides in the legitimate marketplace.</P>
                <P>The primary costs associated with this proposed rule would be the annual registration fee for list I chemicals ($3,699 for manufacturers and $1,850 for distributors, importers, and exporters). However, any manufacturer that handles phenethyl halides for legitimate pharmaceutical fentanyl production should already be registered with DEA and have all security and other handling processes in place which result in minimal cost to those entities.</P>
                <P>DEA has identified 120 domestic suppliers of phenethyl halides based on an internal search of the CAS SciFinder chemical compound database. Thirteen suppliers of phenethyl halides are already registered to handle list I chemicals per DEA's registration system. The remaining suppliers of each of the phenethyl halides are not registered with DEA to handle list I chemicals. It is difficult to estimate the quantity of phenethyl halides these suppliers distribute. It is also common for chemical distributors to have items in their catalogs while not actually having any realized sales. If this proposed rule is finalized, these suppliers are expected to choose the least costly option, and stop selling minimal quantities, if any, of phenethyl halides, rather than incur the registration cost.</P>
                <P>In summary, DEA conducted a qualitative analysis of this proposed rule. DEA believes this proposed action, if finalized, will minimize the diversion of phenethyl halides. DEA believes the market for phenethyl halides for the legitimate manufacturing of pharmaceutical fentanyl is minimal. Additionally, any entity that uses phenethyl halides for legitimate pharmaceutical fentanyl production would be already registered with DEA and have all security and other handling processes in place which results in minimal cost to those entities. Therefore, any potential cost as a result of this regulation is minimal.</P>
                <HD SOURCE="HD2">Executive Order 12988, Civil Justice Reform</HD>
                <P>This proposed regulation meets the applicable standards set forth in sections 3(a) and 3(b)(2) of E.O. 12988 Civil Justice Reform to eliminate drafting errors and ambiguity, minimize litigation, provide a clear legal standard for affected conduct, and promote simplification and burden reduction.</P>
                <HD SOURCE="HD2">Executive Order 13132, Federalism</HD>
                <P>This proposed rulemaking does not have federalism implications warranting the application of E.O. 13132. The proposed rule does not have substantial direct effects on the States, on the relationship between the national Government and the States, or the distribution of power and responsibilities among the various levels of government.</P>
                <HD SOURCE="HD2">Executive Order 13175, Consultation and Coordination With Indian Tribal Governments</HD>
                <P>This proposed rule does not have tribal implications warranting the application of E.O. 13175. This proposed rule does not have substantial direct effects on one or more Indian tribes, on the relationship between the Federal government and Indian tribes, or on the distribution of power and responsibilities between the Federal government and Indian tribes.</P>
                <HD SOURCE="HD2">Regulatory Flexibility Act</HD>
                <P>The Administrator, in accordance with the Regulatory Flexibility Act, 5 U.S.C. 601-612, has reviewed this rule and by approving it, certifies that it will not have a significant economic impact on a substantial number of small entities.</P>
                <P>
                    As discussed above, if finalized as proposed, phenethyl halides and chemical mixtures containing phenethyl halides will be subject to all of the regulatory controls and administrative, civil, and criminal sanctions applicable to the manufacture, distribution, importing, and exporting of list I chemicals. If finalized, it will affect all business activities that handle phenethyl halides including manufacturers, distributors, importers, and exporters. As aforementioned, DEA identified 120 domestic suppliers of which 89 percent (107) are not registered with DEA to handle list I chemicals. All non-registered entities will be affected by this rule. Because DEA does not know the size of these entities, DEA conservatively assumes they are small entities based on the Small Business Administration classification for Other Chemical and Allied Products Merchant Wholesalers (NAICS classification code 424690); entities in this industry are considered small entities if they employee less than 175 employees.
                    <SU>29</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         U.S. Small Business Administration, Table of size standards, Version March 2023, Effective: March 17, 2023, 
                        <E T="03">https://www.sba.gov/document/support-table-size-standards.</E>
                    </P>
                </FTNT>
                <P>
                    The primary cost associated with this rule is the registration cost. Phenethyl halides may be used as an intermediary in various industries, including the manufacturing of fentanyl. Any entity that currently manufactures, distributes, imports, or exports phenethyl halides for pharmaceutical and industrial purposes would already be registered with DEA and have all security and other handling processes in place which result in minimal cost. However, this rule would only impose regulations on those who manufacture, distribute, import, or export phenethyl halides and not end users who are using the chemical as an intermediate. Additionally, entities may submit an application, and request approval for exemption of their chemical mixture containing phenethyl halides in accordance with 21 CFR 1310.13 (exemption of chemical mixtures by 
                    <PRTPAGE P="42398"/>
                    application) or through meeting the requirements stated in 21 CFR 1310.12(d) (automatic exemptions).
                </P>
                <P>DEA believes the sales of the non-registered suppliers are minimal based on the number of comments from the ANPRM. Also, it is common for chemical distributors to have items in their catalog while not actually having any realized sales. Therefore, DEA estimates the cost of this rule on any affected small entity is minimal. DEA welcomes any public comments regarding this estimate.</P>
                <P>
                    Lastly, per the Statistics of U.S. Businesses annual data tables, there are 5,307 small entities under 424690 Other Chemical and Allied Products Merchant Wholesalers.
                    <SU>30</SU>
                    <FTREF/>
                     The number of small entities affected by this proposed rule is 2.02 percent of all the small businesses in this industry.
                    <SU>31</SU>
                    <FTREF/>
                     Based on these factors, DEA projects that this rule, if promulgated, will not result in a significant economic impact on a substantial number of small entities.
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         2021 SUSB Annual Data Tables by Establishment Industry, 
                        <E T="03">https://www.census.gov/data/tables/2021/econ/susb/2021-susb-annual.html,</E>
                         accessed: 03/11/2025.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         Assuming all of the 107 non-registered suppliers are small businesses, the percent of small businesses affected by this rule is 107/5,307 = 2.02%
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act of 1995</HD>
                <P>
                    On the basis of information contained in the “Regulatory Flexibility Act” section above, DEA has determined and certifies pursuant to the Unfunded Mandates Reform Act of 1995 (UMRA), 2 U.S.C. 1501 
                    <E T="03">et seq.,</E>
                     that this action would not result in any Federal mandate that may result “in the expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100,000,000 or more (adjusted for inflation) in any one year. . . .” Therefore, neither a Small Government Agency Plan nor any other action is required under provisions of UMRA.
                </P>
                <HD SOURCE="HD2">Paperwork Reduction Act of 1995</HD>
                <P>This action does not impose any new or revised “collection[s] of information” as defined by the Paperwork Reduction Act of 1995, 44 U.S.C. 3502(3). This action would not impose recordkeeping or reporting requirements on State or local governments, individuals, businesses, or organizations. 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>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 21 CFR Part 1310</HD>
                    <P>Administrative practice and procedure, Drug traffic control, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <P>For the reasons set out above, DEA proposes to amend 21 CFR part 1310 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 1310—RECORDS AND REPORTS OF LISTED CHEMICALS AND CERTAIN MACHINES; IMPORTATION AND EXPORTATION OF CERTAIN MACHINES</HD>
                </PART>
                <AMDPAR>1. The authority citation for 21 CFR part 1310 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>21 U.S.C. 802, 827(h), 830, 871(b), 890.</P>
                </AUTH>
                <AMDPAR>2. In § 1310.02, add paragraph (a)(43) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1310.02 </SECTNO>
                    <SUBJECT>Substances covered.</SUBJECT>
                    <STARS/>
                    <P>(a) * * *</P>
                    <STARS/>
                    <GPOTABLE COLS="2" OPTS="L1,tp0,p1,8/9,i1" CDEF="s150,12">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1"> </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22"> </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         *</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                (43) Phenethyl halides (
                                <E T="03">i.e.,</E>
                                 phenethyl bromide, phenethyl chloride, phenethyl iodide, and phenethyl fluoride)
                            </ENT>
                            <ENT>8338</ENT>
                        </ROW>
                    </GPOTABLE>
                    <STARS/>
                </SECTION>
                <AMDPAR>3. In § 1310.04:</AMDPAR>
                <AMDPAR>a. Redesignate paragraphs (g)(1)(xv), (g)(1)(xvi), (g)(xvii), (g)(1)(xviii), (g)(1)(xix), (g)(1)(xx), (g)(1)(xxi), and (g)(1)(xxii) as paragraphs (g)(1)(xvi), (g)(1)(xvii), (g)(1)(xviii), (g)(1)(xix), (g)(1)(xx), (g)(1)(xxi), (g)(1)(xxii), and (g)(1)(xxiii), respectively; and</AMDPAR>
                <AMDPAR>b. Add new paragraphs (g)(1)(xv) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1310.04 </SECTNO>
                    <SUBJECT>Maintenance of records.</SUBJECT>
                    <STARS/>
                    <P>(g) * * *</P>
                    <P>(1) * * *</P>
                    <P>
                        (xv) Phenethyl halides (
                        <E T="03">i.e.,</E>
                         phenethyl bromide, phenethyl chloride, phenethyl iodide, and phenethyl fluoride)
                    </P>
                    <STARS/>
                </SECTION>
                <AMDPAR>4. In § 1310.09 add new paragraph (v) to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 1310.09 </SECTNO>
                    <SUBJECT>Temporary exemption from registration.</SUBJECT>
                    <STARS/>
                    <P>(v)(1) Each person required under 21 U.S.C. 822 and 21 U.S.C. 957 to obtain a registration to manufacture, distribute, import, or export phenethyl halides, including regulated chemical mixtures pursuant to § 1310.12, is temporarily exempted from the registration requirement, provided that DEA receives a properly completed application for registration or application for exemption for a chemical mixture containing phenethyl halides pursuant to § 1310.13 on or before 30 days after the publication of a rule finalizing this action. The exemption would remain in effect for each person who has made such application until the Administration has approved or denied that application. This exemption applies only to registration; all other chemical control requirements set forth in the Act and parts 1309, 1310, 1313, and 1316 of this chapter remain in full force and effect.</P>
                    <P>(2) Any person who manufactures, distributes, imports, or exports a chemical mixture containing phenethyl halides whose application for exemption is subsequently denied by DEA must obtain a registration with DEA. A temporary exemption from the registration requirement will also be provided for those persons whose application for exemption is denied, provided that DEA receives a properly completed application for registration on or before 30 days following the date of official DEA notification that the application for exemption has been denied. The temporary exemption for such persons would remain in effect until DEA takes final action on their registration application.</P>
                    <STARS/>
                </SECTION>
                <AMDPAR>5. Section 1310.12 is amended by adding in alphabetical order in the table in paragraph (c) an entry for phenethyl halides, to read as follows:</AMDPAR>
                <STARS/>
                <SECTION>
                    <SECTNO>§ 1310.12 </SECTNO>
                    <SUBJECT>Exempt chemical mixtures.</SUBJECT>
                    <STARS/>
                    <P>
                        (c) * * *
                        <PRTPAGE P="42399"/>
                    </P>
                    <GPOTABLE COLS="4" OPTS="L1,i1" CDEF="s100,12,r50,r50">
                        <TTITLE>Table of Concentration Limits</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">
                                DEA chemical
                                <LI>code No.</LI>
                            </CHED>
                            <CHED H="1">Concentration</CHED>
                            <CHED H="1">Special conditions</CHED>
                        </BOXHD>
                        <ROW EXPSTB="03" RUL="s">
                            <ENT I="21">
                                <E T="02">List I Chemicals</E>
                            </ENT>
                        </ROW>
                        <ROW EXPSTB="00">
                            <ENT I="22"> </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         *</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                Phenethyl halides (
                                <E T="03">i.e.,</E>
                                 phenethyl bromide, phenethyl chloride, phenethyl iodide, and phenethyl fluoride)
                            </ENT>
                            <ENT>8338</ENT>
                            <ENT>Not exempt at any concentration</ENT>
                            <ENT>Chemical mixtures containing any amount of phenethyl halides (i.e. phenethyl bromide, phenethyl chloride, phenethyl iodide, and phenethyl fluoride) are not exempt.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         *</ENT>
                        </ROW>
                    </GPOTABLE>
                    <STARS/>
                    <HD SOURCE="HD1">Signing Authority</HD>
                    <P>
                        This document of the Drug Enforcement Administration was signed on June 30, 2026, by Administrator Terrance Cole. That document with the original signature and date is maintained by DEA. For administrative purposes only, and in compliance with requirements of the Office of the Federal Register, the undersigned DEA Federal Register Liaison Officer has been authorized to sign and submit the document in electronic format for publication, as an official document of DEA. This administrative process in no way alters the legal effect of this document upon publication in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                </SECTION>
                <SIG>
                    <NAME>Leslie Mayer,</NAME>
                    <TITLE>Federal Register Liaison Officer, Drug Enforcement Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13825 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-09-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 52</CFR>
                <DEPDOC>[EPA-R09-OAR-2026-3400; FRL-13355-01-R9]</DEPDOC>
                <SUBJECT>Approval and Promulgation of Implementation Plans; California; San Joaquin Valley; Revisions to Motor Vehicle Emissions Budgets for Ozone</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Environmental Protection Agency (EPA) is proposing to approve revisions to the State of California's State Implementation Plan (SIP) for the San Joaquin Valley (SJV) area. The revisions consist of an update to the SJV area's motor vehicle emissions budgets (“budgets”) for nitrogen oxides (NO
                        <E T="52">X</E>
                        ) and volatile organic compounds (VOC) for the 2008 8-hour ozone national ambient air quality standard (NAAQS or “standard”). These updated budgets for 2026, 2029, and 2031 were developed with the latest modeling method approved for California. These updated budgets apply to all subareas within SJV. If the EPA approves these budgets, they would supersede the existing approved SJV subarea budgets for the 2008 ozone NAAQS that were based on an earlier emissions model. The EPA is proposing to approve the updated SJV ozone budgets in accordance with the requirements of the Clean Air Act (CAA or “Act”) and the EPA's regulations.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must arrive on or before August 10, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, identified by Docket ID No. EPA-R09-OAR-2026-3400 at 
                        <E T="03">https://www.regulations.gov.</E>
                         For comments submitted at 
                        <E T="03">Regulations.gov,</E>
                         follow the online instructions for submitting comments. Once submitted, comments cannot be edited or removed from 
                        <E T="03">Regulations.gov.</E>
                         The EPA may publish any comment received to its public docket. Do not submit electronically any information you consider to be Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. Multimedia submissions (audio, video, etc.) must be accompanied by a written comment. The written comment is considered the official comment and should include discussion of all points you wish to make. The EPA will generally not consider comments or comment contents located outside of the primary submission (
                        <E T="03">i.e.,</E>
                         on the web, cloud, or other file sharing system). For additional submission methods, please contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section. For the full EPA public comment policy, information about CBI or multimedia submissions, and general guidance on making effective comments, please visit 
                        <E T="03">https://www.epa.gov/dockets/commenting-epa-dockets.</E>
                         If you need assistance in a language other than English or if you are a person with a disability who needs a reasonable accommodation at no cost to you, please contact the person identified in the 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Lindsay Wickersham, Air Planning Office (ARD-2), EPA Region IX, 75 Hawthorne Street, San Francisco, CA 94105, (415) 947-4192, or by email at 
                        <E T="03">Wickersham.Lindsay@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Throughout this document, “we,” “us,” and “our” refer to the EPA.</P>
                <HD SOURCE="HD1">Table of Contents</HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. Background</FP>
                    <FP SOURCE="FP1-2">A. Standard and Geographic Area Applicable to This Action</FP>
                    <FP SOURCE="FP1-2">B. Motor Vehicle Emissions Budgets and Transportation Conformity</FP>
                    <FP SOURCE="FP1-2">C. Existing Approved Budgets</FP>
                    <FP SOURCE="FP1-2">D. Submission of Revised Budgets Based on EMFAC2021 and Off-Model Adjustment Factors</FP>
                    <FP SOURCE="FP-2">II. Clean Air Act Procedural and Administrative Requirements for SIP Submittals and Criteria for Approval of Revised Budgets</FP>
                    <FP SOURCE="FP-2">III. Revised Motor Vehicle Emissions Budgets for the 2008 8-Hour Ozone Standard</FP>
                    <FP SOURCE="FP1-2">A. Review of Revised Budgets for the 2008 8-Hour Ozone Standard</FP>
                    <FP SOURCE="FP1-2">B. Summary of Changes to Budgets and the EPA's Analysis of the State's Submittal</FP>
                    <FP SOURCE="FP-2">IV. Proposed Action and Request for Public Comment</FP>
                    <FP SOURCE="FP-2">V. Statutory and Executive Order Reviews</FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. Background</HD>
                <HD SOURCE="HD2">A. Standard and Geographic Area Applicable to This Action</HD>
                <P>
                    In 2008, the EPA revised the ozone NAAQS by setting the acceptable level of ozone in the ambient air at 0.075 
                    <PRTPAGE P="42400"/>
                    parts per million (ppm), averaged over an 8-hour period.
                    <SU>1</SU>
                    <FTREF/>
                     Following promulgation of a new or revised NAAQS, the EPA is required under CAA section 107(d) to designate areas throughout the country as attaining or not attaining the NAAQS. In 2012, the EPA designated the San Joaquin Valley as nonattainment for the 2008 8-hour ozone standard and classified the area as “Extreme.” 
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         73 FR 16436 (March 27, 2008).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         77 FR 30088 (May 21, 2012), and 40 CFR 81.305.
                    </P>
                </FTNT>
                <P>
                    The SJV nonattainment area for the 2008 8-hour ozone standard consists of San Joaquin, Stanislaus, Merced, Madera, Fresno, Tulare, and Kings Counties, and the western portion of Kern County. The San Joaquin Valley nonattainment area stretches over 250 miles from north to south, averages a width of 80 miles, and encompasses over 23,000 square miles. It is partially enclosed by the Coast Mountain range to the west, the Tehachapi Mountains to the south, and the Sierra Nevada range to the east.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         For a precise definition of the boundaries of the San Joaquin Valley nonattainment area for the 2008 8-hour ozone NAAQS, see 40 CFR 81.305.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Motor Vehicle Emissions Budgets and Transportation Conformity</HD>
                <P>
                    Under the CAA, States are required to submit, at various times, control strategy SIP revisions and maintenance plans for nonattainment and maintenance areas for a given NAAQS. These emission control strategy SIP revisions (
                    <E T="03">e.g.,</E>
                     reasonable further progress (RFP) and attainment demonstration SIP revisions) and maintenance plans include motor vehicle emissions budgets for criteria pollutants and/or their precursors to address pollution from cars and trucks. The motor vehicle emissions budgets are the portions of the total allowable emissions that are allocated to on-road vehicle use that, together with emissions from other sources in the area, will provide for RFP, attainment or maintenance.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         See the definition of “motor vehicle emissions budget” at 40 CFR 93.101.
                    </P>
                </FTNT>
                <P>
                    Under section 176(c) of the CAA, transportation plans, Transportation Improvement Programs (TIPs), and transportation projects must “conform” to (
                    <E T="03">i.e.,</E>
                     be consistent with) the SIP before they can be adopted or approved. Conformity to the SIP means that transportation activities will not cause new air quality violations, worsen existing air quality violations, or delay timely attainment of the NAAQS or delay an interim milestone.
                </P>
                <P>Actions involving Federal Highway Administration (FHWA) or Federal Transit Administration (FTA) funding or approval are subject to the EPA's transportation conformity rule, codified at 40 CFR part 93, subpart A. Under the transportation conformity rule, Metropolitan Planning Organizations (MPOs) in nonattainment and maintenance areas coordinate with State and local air quality and transportation agencies, the EPA, the FHWA, and the FTA to demonstrate that an area's regional transportation plans and TIPs conform to the applicable SIP. This demonstration is typically done by showing that estimated emissions from existing and planned highway and transit systems are less than or equal to the budgets contained in all control strategy SIPs.</P>
                <P>
                    In California, budgets are derived using a computer model developed by the California Air Resources Board (CARB) and referred to as EMFAC (short for EMission FACtor). EMFAC is used to calculate current and future inventories of motor vehicle emissions at the State, air district, air basin, county, and project level. The EPA approved EMFAC2021 for use in SIP revisions and transportation conformity determinations in California in November 2022.
                    <SU>5</SU>
                    <FTREF/>
                     The EPA approved off-model adjustment factors to EMFAC2021 in November 2025.
                    <SU>6</SU>
                    <FTREF/>
                     With the approval of the adjustment factors, EMFAC2021 with these adjustment factors is the latest approved method for modeling emissions available in California, per 40 CFR 93.111.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         87 FR 68483 (November 15, 2022) (EPA approval and notice of availability for EMFAC2021).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Letter titled “EPA Region 9 letter approving EMFAC2021 Adjustment Factors that remove the emissions benefits of the Advanced Clean Trucks, Heavy-Duty Omnibus, and other regulations,” from Anita Lee, Acting Director, Air and Radiation Division, EPA Region IX, to Edie Chang, Deputy Executive Officer, CARB, November 21, 2025. A copy of this letter can be found on the EPA's Policy and Technical Guidance for State and Local Transportation site, 
                        <E T="03">https://www.epa.gov/state-and-local-transportation/policy-and-technical-guidance-state-and-local-transportation.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Existing Approved Budgets</HD>
                <P>
                    The EPA previously approved the NO
                    <E T="52">X</E>
                     and VOC budgets for SJV for the 2008 8-hour ozone standard. The EPA approved the budgets as part of the EPA's approval of three SIP revisions submitted by CARB to address the nonattainment planning requirements for the SJV for the 2008 ozone NAAQS, including the RFP and attainment demonstrations. These SIP revisions include the “San Joaquin Valley 2016 Plan for the 2008 8-Hour Ozone Standard” (“2016 Ozone Plan”) and the portions of the “Revised Proposed 2016 State Strategy for the State Implementation Plan” (“2016 State SIP Strategy”) and “2018 Updates to the California State Implementation Plan” (“2018 SIP Update”) that pertain to the San Joaquin Valley for the 2008 ozone NAAQS.
                    <SU>7</SU>
                    <FTREF/>
                     Collectively, we refer to the approved SIP revisions for SJV for the 2008 ozone NAAQS as the “2016 SJV Ozone SIP.”
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         We approved portions of the 2016 Ozone Plan and 2016 State SIP Strategy as meeting certain requirements, including the attainment demonstration, at 84 FR 3302 (February 12, 2019). We approved portions of the 2016 Ozone Plan and the 2018 SIP Update as meeting certain other requirements, including the RFP demonstration at 84 FR 11198 (March 25, 2019), as corrected at 84 FR 19680 (May 3, 2019). We approved the budgets contained in the 2018 SIP Update as part of our approval published at 84 FR 11198 (March 25, 2019).
                    </P>
                </FTNT>
                <P>
                    These approved ozone budgets were developed using EMFAC2014, but the 2020 and later budgets for certain SJV county-subareas reflected safety margins to accommodate the then-expected approval of EMFAC2017.
                    <SU>8</SU>
                    <FTREF/>
                     In the SJV, the eight county-level MPOs, FHWA, and FTA are the relevant transportation agencies that must use applicable approved or adequate budgets in determining the conformity of transportation plans and TIPs within the SJV region.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         2018 SIP Update, pp. 8 and 55.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. Submission of Revised Budgets Based on EMFAC2021 and Off-Model Adjustment Factors</HD>
                <P>
                    On March 26, 2026, CARB adopted revised budgets that were developed using EMFAC2021 and the November 21, 2025 adjustment factors.
                    <SU>9</SU>
                    <FTREF/>
                     These revised budgets, which were adopted in a document titled 
                    <E T="03">2026 Updates to Motor Vehicle Emissions Budgets for the San Joaquin Valley 75 Parts Per Billion Ozone State Implementation Plan</E>
                     (“2026 Valley Ozone Budget Update”), were submitted to the EPA on April 30, 2026.
                    <SU>10</SU>
                    <FTREF/>
                     In addition, CARB requested that the EPA's approval allow the budgets in the 2026 Valley Ozone Budget Update to be superseded by the next budgets found to be adequate by the EPA (
                    <E T="03">e.g.,</E>
                     that are based on the next version of EMFAC), per 40 CFR 93.118(e)(1).
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         CARB Resolution No. 26-2, March 26, 2026.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Letter dated April 30, 2026, from Stephen S. Cliff, Executive Officer, California Air Resources Board, to Michael Martucci, Acting Regional Administrator, EPA Region IX.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         CARB's request to limit the duration of the approval of the budgets in the 2026 Ozone Plan Update is contained in the transmittal letter dated April 30, 2026, from Stephen S. Cliff, Executive Officer, California Air Resources Board, to Michael Martucci, Acting Regional Administrator, EPA Region IX. The transportation conformity regulation at 40 CFR 93.118(e)(1) allows submitted budgets that EPA has found to be adequate to supersede 
                        <PRTPAGE/>
                        previously approved budgets if EPA specifies this in its approval of a SIP with those prior budgets.
                    </P>
                </FTNT>
                <PRTPAGE P="42401"/>
                <HD SOURCE="HD1">II. Clean Air Act Procedural and Administrative Requirements for SIP Submittals and Criteria for Approval of Revised Budgets</HD>
                <P>CAA sections 110(a)(1) and (2) and 110(l) require a State to provide reasonable public notice and opportunity for public hearing prior to the adoption and submittal of a SIP or SIP revision. To meet this requirement, every SIP submittal should include evidence that adequate public notice was given and an opportunity for a public hearing was provided, consistent with the EPA's implementing regulations in 40 CFR 51.102.</P>
                <P>CARB satisfied applicable statutory and regulatory requirements for reasonable public notice and hearing prior to adoption and submittal of the revised budgets. In the documentation included as part of the April 30, 2026 SIP revision submittal, CARB provided evidence of the required public notice and opportunity for public comment prior to its March 26, 2026 public hearing and adoption of the revised budgets. We find, therefore, that the submittal of the revised budgets meets the procedural requirements for public notice and hearing in CAA sections 110(a) and 110(l).</P>
                <P>
                    Under section 110(l) of the CAA, SIP revisions must not interfere with any applicable requirements concerning attainment or RFP or any other applicable requirement of the Act. Generally, the EPA reviews budgets for approval in the context of the Agency's review of a control strategy implementation plan (
                    <E T="03">i.e.,</E>
                     attainment or RFP plan) or maintenance plan. In addition, revisions to budgets can be approved without comprehensive updates to the related control strategy implementation or maintenance plan if the plan, including the revised budgets, continues to meet applicable requirements (
                    <E T="03">i.e.,</E>
                     RFP, attainment, or maintenance).
                </P>
                <P>
                    A State may revise the motor vehicle emissions inventories and related budgets without revising its entire SIP, consistent with section 110(l), if: (1) the SIP continues to meet applicable requirements when the previous motor vehicle emissions inventories are replaced with new base year and milestone, attainment, or maintenance year inventories based on a more recent emissions model; and (2) the State can document that growth and control strategy assumptions for non-motor vehicle sources continue to be valid and any minor updates do not change the overall conclusions of the SIP.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         See examples of EPA rules involving replacement of budgets in response to an emissions model update, 
                        <E T="03">e.g.,</E>
                         Allentown-Bethlehem-Easton (79 FR 28435, May 16, 2014) and Beaumont/Port Arthur (78 FR 7672, February 4, 2013).
                    </P>
                </FTNT>
                <P>
                    In this proposed rulemaking, the EPA is not making a separate adequacy finding for the revised budgets that were submitted in the 2026 SJV Ozone Budget Update because the budgets they would replace are approved budgets from the 2016 SJV Ozone SIP (see 40 CFR 93.118(e)(1)).
                    <SU>13</SU>
                    <FTREF/>
                     However, the budgets in the 2026 SJV Ozone Budget Update do meet the criteria in 40 CFR 93.118(e)(4),
                    <SU>14</SU>
                    <FTREF/>
                     and therefore the EPA is proposing to approve them. If this proposal is finalized, these budgets would replace all the motor vehicle emissions budgets in the 2016 SJV Ozone SIP.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         NO
                        <E T="52">X</E>
                         and VOC budgets for the SJV area with respect to the 2008 8-hour ozone standard were previously approved and found adequate effective April 24, 2019. See 84 FR 11198.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         The adequacy criteria in 40 CFR 93.118(e) include endorsement by the Governor (or designee); prior consultation among relevant air and transportation agencies; clear identification and precise quantification of the budgets; consistency of the budgets, when considered with all other emissions sources, with applicable requirements for RFP, attainment or maintenance; consistency with and clear relation to the emissions inventory and control measures; and explanation and documentation of changes relative to previously submitted budgets.
                    </P>
                </FTNT>
                <P>The EPA is also proposing that, once approved, these budgets could be superseded by future adequate budgets, as CARB requested and as allowed by the transportation conformity regulation at 40 CFR 93.118(e)(1). This would allow new information included in the next version of EMFAC, once approved, to be incorporated into the conformity process as soon as the EPA determines that updated budgets are adequate, instead of having to wait until updated budgets are approved.</P>
                <HD SOURCE="HD1">III. Revised Motor Vehicle Emissions Budgets for the 2008 8-Hour Ozone Standard</HD>
                <HD SOURCE="HD2">A. Review of Revised Budgets for the 2008 8-Hour Ozone Standard</HD>
                <P>
                    Table 1 of this document lists the revised budgets by subarea for the SJV for the 2008 8-hour ozone standard. CARB developed the revised budgets using EMFAC2021 with the November 2025 adjustment factors 
                    <SU>15</SU>
                    <FTREF/>
                     and the travel activity projections provided by the San Joaquin Valley MPOs consistent with the 2025 Federal TIP.
                    <SU>16</SU>
                    <FTREF/>
                     As such, we find that the revised budgets reflect the most recent planning forecasts and are based on the most recent emission factor data and approved calculation methods. A comparison of the existing approved budgets with the revised budgets and a discussion of the EPA's proposed action on the revised budgets is provided below in section III.B of this document.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         See section I.B of this document for information concerning EPA approval of EMFAC2021 and the November 2025 adjustment factors.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         More information on each SJV MPO's 2025 Federal TIP can be found on their respective websites. The Fresno Council of Governments (FCOG), Kern Council of Governments (KCOG), Kings County Association of Governments (KCAG), Madera County Transportation Commission (MCTC), Merced County Association of Governments (MCAG), San Joaquin Council of Governments (SJCOG), Stanislaus Council of Governments (StanCOG), and the Tulare County Association of Governments (TCAG) adopted their 2025 Federal TIPs between May and August, 2024.
                    </P>
                </FTNT>
                <GPOTABLE COLS="7" OPTS="L2,nj,i1" CDEF="s50,11,11,11p,11,11,11">
                    <TTITLE>
                        Table 1—San Joaquin Valley Revised Budgets Developed Using EMFAC2021 With November 2025 Adjustment Factors 
                        <E T="01">
                            <SU>a</SU>
                        </E>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">County subarea</CHED>
                        <CHED H="1">2008 8-hour ozone standard</CHED>
                        <CHED H="2">
                            NO
                            <E T="0732">X</E>
                            <LI>(tons per average summer day)</LI>
                        </CHED>
                        <CHED H="3">2026</CHED>
                        <CHED H="3">2029</CHED>
                        <CHED H="3">2031</CHED>
                        <CHED H="2">
                            VOC
                            <LI>(tons per average summer day)</LI>
                        </CHED>
                        <CHED H="3">2026</CHED>
                        <CHED H="3">2029</CHED>
                        <CHED H="3">2031</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Fresno</ENT>
                        <ENT>8.4</ENT>
                        <ENT>7.8</ENT>
                        <ENT>7.6</ENT>
                        <ENT>4.4</ENT>
                        <ENT>3.9</ENT>
                        <ENT>3.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kern (SJV)</ENT>
                        <ENT>10.6</ENT>
                        <ENT>10.3</ENT>
                        <ENT>10.3</ENT>
                        <ENT>3.7</ENT>
                        <ENT>3.3</ENT>
                        <ENT>3.1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kings</ENT>
                        <ENT>2.1</ENT>
                        <ENT>2.1</ENT>
                        <ENT>2.1</ENT>
                        <ENT>0.8</ENT>
                        <ENT>0.7</ENT>
                        <ENT>0.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Madera</ENT>
                        <ENT>1.9</ENT>
                        <ENT>1.7</ENT>
                        <ENT>1.6</ENT>
                        <ENT>0.9</ENT>
                        <ENT>0.8</ENT>
                        <ENT>0.8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Merced</ENT>
                        <ENT>4.6</ENT>
                        <ENT>4.3</ENT>
                        <ENT>4.3</ENT>
                        <ENT>1.5</ENT>
                        <ENT>1.3</ENT>
                        <ENT>1.2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">San Joaquin</ENT>
                        <ENT>6.0</ENT>
                        <ENT>5.5</ENT>
                        <ENT>5.2</ENT>
                        <ENT>3.5</ENT>
                        <ENT>3.1</ENT>
                        <ENT>2.8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Stanislaus</ENT>
                        <ENT>3.9</ENT>
                        <ENT>3.5</ENT>
                        <ENT>3.3</ENT>
                        <ENT>2.4</ENT>
                        <ENT>2.1</ENT>
                        <ENT>1.9</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42402"/>
                        <ENT I="01">Tulare</ENT>
                        <ENT>3.6</ENT>
                        <ENT>3.2</ENT>
                        <ENT>3.1</ENT>
                        <ENT>2.2</ENT>
                        <ENT>1.9</ENT>
                        <ENT>1.7</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>a</SU>
                         The county-specific budgets are set forth in Table III-1 of the 2026 Valley Ozone Budget Update. CARB rounded up each of the subarea budgets calculated using EMFAC2021 with the off-model adjustment factors approved by the EPA in November 2025 to the nearest tenth of a ton.
                    </TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD2">B. Summary of Changes to Budgets and the EPA's Analysis of the State's Submittal</HD>
                <P>The 2026 Valley Ozone Budget Update includes updated budgets but does not revise any other element of the 2016 SJV Ozone SIP. As noted previously, we believe that a State may revise the motor vehicle emissions inventories and related budgets without revising their entire SIP, consistent with section 110(l), if: (1) the SIP continues to meet applicable requirements when the previous motor vehicle emissions inventories are replaced with new base year and milestone, attainment, or maintenance year inventories based on a more recent emissions model; and (2) the State can document that growth and control strategy assumptions for non-motor vehicle sources continue to be valid and any minor updates do not change the overall conclusions of the SIP. These considerations provide the framework for our evaluation of the revised budgets in the 2026 Valley Ozone Budget Update.</P>
                <P>
                    Tables 2 and 3 of this document compare the existing EPA-approved NO
                    <E T="52">X</E>
                     and VOC subarea budgets developed using EMFAC2014 with the revised subarea budgets developed using EMFAC2021 and the November 2025 adjustment factors. The budgets are provided by subarea and apply to the 2008 8-hour ozone standard.
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         The transportation conformity regulation allows SIPs to establish budgets for geographic subareas of a nonattainment area in 40 CFR 93.124(c).
                    </P>
                </FTNT>
                <GPOTABLE COLS="10" OPTS="L2,nj,i1" CDEF="s50,8,8,10p,8,8,10p,8,8,10">
                    <TTITLE>
                        Table 2—Comparison of San Joaquin Valley Ozone Budgets for NO
                        <E T="0732">X</E>
                         for the 2008 8-Hour Ozone Standard
                    </TTITLE>
                    <TDESC>[Tons per average summer day]</TDESC>
                    <BOXHD>
                        <CHED H="1">County subarea</CHED>
                        <CHED H="1">2026</CHED>
                        <CHED H="2">Existing</CHED>
                        <CHED H="2">Revised</CHED>
                        <CHED H="2">Net change</CHED>
                        <CHED H="1">2029</CHED>
                        <CHED H="2">Existing</CHED>
                        <CHED H="2">Revised</CHED>
                        <CHED H="2">Net change</CHED>
                        <CHED H="1">2031</CHED>
                        <CHED H="2">Existing</CHED>
                        <CHED H="2">Revised</CHED>
                        <CHED H="2">Net change</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Fresno</ENT>
                        <ENT>13.2</ENT>
                        <ENT>8.4</ENT>
                        <ENT>−4.8</ENT>
                        <ENT>12.4</ENT>
                        <ENT>7.8</ENT>
                        <ENT>−4.6</ENT>
                        <ENT>12.1</ENT>
                        <ENT>7.6</ENT>
                        <ENT>−4.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kern (SJV)</ENT>
                        <ENT>14.4</ENT>
                        <ENT>10.6</ENT>
                        <ENT>−3.8</ENT>
                        <ENT>14.3</ENT>
                        <ENT>10.3</ENT>
                        <ENT>−4.0</ENT>
                        <ENT>14.3</ENT>
                        <ENT>10.3</ENT>
                        <ENT>−4.0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kings</ENT>
                        <ENT>2.6</ENT>
                        <ENT>2.1</ENT>
                        <ENT>−0.5</ENT>
                        <ENT>2.6</ENT>
                        <ENT>2.1</ENT>
                        <ENT>−0.5</ENT>
                        <ENT>2.6</ENT>
                        <ENT>2.1</ENT>
                        <ENT>−0.5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Madera</ENT>
                        <ENT>2.5</ENT>
                        <ENT>1.9</ENT>
                        <ENT>−0.6</ENT>
                        <ENT>2.4</ENT>
                        <ENT>1.7</ENT>
                        <ENT>−0.7</ENT>
                        <ENT>2.3</ENT>
                        <ENT>1.6</ENT>
                        <ENT>−0.7</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Merced</ENT>
                        <ENT>5.9</ENT>
                        <ENT>4.6</ENT>
                        <ENT>−1.3</ENT>
                        <ENT>5.6</ENT>
                        <ENT>4.3</ENT>
                        <ENT>−1.3</ENT>
                        <ENT>5.4</ENT>
                        <ENT>4.3</ENT>
                        <ENT>−1.1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">San Joaquin</ENT>
                        <ENT>7.0</ENT>
                        <ENT>6.0</ENT>
                        <ENT>−1.0</ENT>
                        <ENT>6.6</ENT>
                        <ENT>5.5</ENT>
                        <ENT>−1.1</ENT>
                        <ENT>6.3</ENT>
                        <ENT>5.2</ENT>
                        <ENT>−1.1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Stanislaus</ENT>
                        <ENT>4.9</ENT>
                        <ENT>3.9</ENT>
                        <ENT>−1.0</ENT>
                        <ENT>4.5</ENT>
                        <ENT>3.5</ENT>
                        <ENT>−1.0</ENT>
                        <ENT>4.3</ENT>
                        <ENT>3.3</ENT>
                        <ENT>−1.0</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Tulare</ENT>
                        <ENT>4.0</ENT>
                        <ENT>3.6</ENT>
                        <ENT>−0.4</ENT>
                        <ENT>3.7</ENT>
                        <ENT>3.2</ENT>
                        <ENT>−0.5</ENT>
                        <ENT>3.5</ENT>
                        <ENT>3.1</ENT>
                        <ENT>−0.4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Totals</ENT>
                        <ENT>54.5</ENT>
                        <ENT>41.1</ENT>
                        <ENT>−13.4</ENT>
                        <ENT>52.1</ENT>
                        <ENT>38.4</ENT>
                        <ENT>−13.7</ENT>
                        <ENT>50.8</ENT>
                        <ENT>37.5</ENT>
                        <ENT>−13.3</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="10" OPTS="L2,nj,i1" CDEF="s50,8,8,10p,8,8,10p,8,8,10">
                    <TTITLE>Table 3—Comparison of San Joaquin Valley Ozone Budgets for VOC for the 2008 8-Hour Ozone Standard</TTITLE>
                    <TDESC>[Tons per average summer day]</TDESC>
                    <BOXHD>
                        <CHED H="1">County subarea</CHED>
                        <CHED H="1">2026</CHED>
                        <CHED H="2">Existing</CHED>
                        <CHED H="2">Revised</CHED>
                        <CHED H="2">Net change</CHED>
                        <CHED H="1">2029</CHED>
                        <CHED H="2">Existing</CHED>
                        <CHED H="2">Revised</CHED>
                        <CHED H="2">Net change</CHED>
                        <CHED H="1">2031</CHED>
                        <CHED H="2">Existing</CHED>
                        <CHED H="2">Revised</CHED>
                        <CHED H="2">Net change</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Fresno</ENT>
                        <ENT>4.9</ENT>
                        <ENT>4.4</ENT>
                        <ENT>−0.5</ENT>
                        <ENT>4.5</ENT>
                        <ENT>3.9</ENT>
                        <ENT>−0.6</ENT>
                        <ENT>4.2</ENT>
                        <ENT>3.6</ENT>
                        <ENT>−0.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kern (SJV)</ENT>
                        <ENT>4.2</ENT>
                        <ENT>3.7</ENT>
                        <ENT>−0.5</ENT>
                        <ENT>4.0</ENT>
                        <ENT>3.3</ENT>
                        <ENT>−0.7</ENT>
                        <ENT>3.9</ENT>
                        <ENT>3.1</ENT>
                        <ENT>−0.8</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kings</ENT>
                        <ENT>0.9</ENT>
                        <ENT>0.8</ENT>
                        <ENT>−0.1</ENT>
                        <ENT>0.8</ENT>
                        <ENT>0.7</ENT>
                        <ENT>−0.1</ENT>
                        <ENT>0.8</ENT>
                        <ENT>0.7</ENT>
                        <ENT>−0.1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Madera</ENT>
                        <ENT>1.0</ENT>
                        <ENT>0.9</ENT>
                        <ENT>−0.1</ENT>
                        <ENT>0.9</ENT>
                        <ENT>0.8</ENT>
                        <ENT>−0.1</ENT>
                        <ENT>0.8</ENT>
                        <ENT>0.8</ENT>
                        <ENT>0.0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Merced</ENT>
                        <ENT>1.5</ENT>
                        <ENT>1.5</ENT>
                        <ENT>0.0</ENT>
                        <ENT>1.3</ENT>
                        <ENT>1.3</ENT>
                        <ENT>0.0</ENT>
                        <ENT>1.2</ENT>
                        <ENT>1.2</ENT>
                        <ENT>0.0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">San Joaquin</ENT>
                        <ENT>3.5</ENT>
                        <ENT>3.5</ENT>
                        <ENT>0.0</ENT>
                        <ENT>3.1</ENT>
                        <ENT>3.1</ENT>
                        <ENT>0.0</ENT>
                        <ENT>2.8</ENT>
                        <ENT>2.8</ENT>
                        <ENT>0.0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Stanislaus</ENT>
                        <ENT>2.2</ENT>
                        <ENT>2.4</ENT>
                        <ENT>0.2</ENT>
                        <ENT>2.0</ENT>
                        <ENT>2.1</ENT>
                        <ENT>0.1</ENT>
                        <ENT>1.8</ENT>
                        <ENT>1.9</ENT>
                        <ENT>0.1</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Tulare</ENT>
                        <ENT>2.1</ENT>
                        <ENT>2.2</ENT>
                        <ENT>0.1</ENT>
                        <ENT>1.8</ENT>
                        <ENT>1.9</ENT>
                        <ENT>0.1</ENT>
                        <ENT>1.7</ENT>
                        <ENT>1.7</ENT>
                        <ENT>0.0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Totals</ENT>
                        <ENT>20.3</ENT>
                        <ENT>19.4</ENT>
                        <ENT>−0.9</ENT>
                        <ENT>18.4</ENT>
                        <ENT>17.1</ENT>
                        <ENT>−1.3</ENT>
                        <ENT>17.2</ENT>
                        <ENT>15.8</ENT>
                        <ENT>−1.4</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    The revised NO
                    <E T="52">X</E>
                     and VOC budgets for 2026, 2029, and 2031 are intended to replace the existing EPA-approved NO
                    <E T="52">X</E>
                     and VOC budgets in the 2016 SJV Ozone SIP developed for the 2008 8-hour ozone standard. A comparison of the 
                    <PRTPAGE P="42403"/>
                    existing budgets with the revised budgets is shown in tables 2 and 3. The tables show that the NO
                    <E T="52">X</E>
                     and VOC regional totals for the revised budgets are less than the NO
                    <E T="52">X</E>
                     and VOC regional totals for the existing budgets for all years. On a subarea basis, there are certain VOC increases, 
                    <E T="03">e.g.,</E>
                     Stanislaus County for years 2026, 2029, and 2031, respectively, and Tulare County for years 2026 and 2029, but RFP and attainment are demonstrated for the San Joaquin Valley on a regional, not a subarea, basis.
                </P>
                <P>
                    First, we note that the 2016 SJV Ozone SIP relied upon motor vehicle emissions inventories, from which the budgets were derived, to demonstrate compliance with RFP and attainment requirements. With respect to the RFP requirement, we found that the 2016 SJV Ozone SIP provided a significant surplus of NO
                    <E T="52">X</E>
                     emissions reductions beyond those necessary to meet the RFP requirement.
                    <SU>18</SU>
                    <FTREF/>
                     As shown in tables 2 and 3, the regional totals for the revised budgets submitted by CARB for NO
                    <E T="52">X</E>
                     and VOC for 2026, 2029, and 2031 are lower than corresponding regional totals for the budgets approved in 2019. As such, the replacement of the existing budgets with the revised budgets would not change the conclusion that the 2016 SJV Ozone SIP meets the requirements for RFP.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         See table 4 of our proposed approval of the 2018 SIP Update, 83 FR 61346, 61353 (November 29, 2018).
                    </P>
                </FTNT>
                <P>
                    Second, the 2026 Valley Ozone Budget Update does not document that growth and control strategy assumptions for non-motor vehicle sources in the 2016 SJV Ozone SIP continue to be valid. However, CARB and the San Joaquin Valley Unified Air Pollution Control District (SJVUAPCD or “District”) have submitted more recent emissions projections of NO
                    <E T="52">X</E>
                     and VOC emissions for San Joaquin Valley to address SIP requirements for the 2015 ozone NAAQS. Such updated emissions projections can be used to document that updates to the emissions estimates for non-motor vehicle sources do not change the overall conclusions of the SIP.
                </P>
                <P>
                    For that purpose, we have prepared updated NO
                    <E T="52">X</E>
                     and VOC emissions inventories from all sources (
                    <E T="03">i.e.,</E>
                     stationary, area, on-road, and non-road sources) in the SJV for 2026, 2029, and 2031. For the most current emissions inventory data, the EPA used the latest available emissions inventory data for stationary, area, and non-road sources, which is from the District's 
                    <E T="03">2022 Plan for the 2015 8-Hour Ozone Standard</E>
                     (adopted December 15, 2022).
                    <SU>19</SU>
                    <FTREF/>
                     For on-road sources, the EPA used the revised budgets from the 2026 Valley Ozone Budget Update. These inventories provide a basis for comparison with the corresponding inventories from the 2016 SJV Ozone SIP.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         CARB submitted the 
                        <E T="03">2022 Plan for the 2015 8-Hour Ozone Standard</E>
                         to the EPA on February 23, 2023. The submission was deemed complete by operation of law on August 23, 2023.
                    </P>
                </FTNT>
                <P>
                    We would expect that most current emissions estimates from all sources in SJV in 2026, 2029, and 2031 would be lower than those included in the 2016 SJV Ozone SIP because they reflect control measures adopted since that plan was approved, and as shown below in tables 4 and 5, the updated regional emissions for 2026, 2029, and 2031, including the revised budgets, are 10.5, 9.4, and 9.9 tons per summer day (tpsd) lower for NO
                    <E T="52">X</E>
                     and 3.0, 9.9, and 9.6 tpsd lower for VOC, respectively, than the corresponding figures in the 2016 SJV Ozone Plan. The current emissions estimates for 2031 (115.2 tpsd NO
                    <E T="52">X</E>
                     and 290.4 tpsd VOC) are consistent with the attainment target level for the 2008 ozone standard (131.9 tpsd NO
                    <E T="52">X</E>
                     and 296.7 tpsd VOC).
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         See table 1 on pages 44531 and 44532 of our proposed rule approving the attainment demonstration for the 2016 SJV Ozone SIP at 83 FR 44528 (August 31, 2018).
                    </P>
                </FTNT>
                <P>
                    Therefore, we find that the 2016 SJV Ozone Plan will continue to meet applicable requirements for RFP and attainment when the existing approved, EMFAC2014-based budgets are replaced with the revised EMFAC2021 budgets with the November 2025 adjustment factors and that the changes in the growth and control strategy assumptions for non-motor vehicle sources do not change the overall conclusions of the 2016 SJV Ozone SIP. As such, we find that approval of the revised NO
                    <E T="52">X</E>
                     and VOC budgets from the 2026 Valley Ozone Budget Update for 2026, 2029, and 2031 as shown in table 1 would not interfere with attainment or RFP or any other requirement of the Act and would thereby comply with section 110(l), and we propose to approve them on that basis.
                </P>
                <GPOTABLE COLS="10" OPTS="L2,nj,i1" CDEF="s50,8,8,8p,8,8,8p,8,8,8">
                    <TTITLE>
                        Table 4—Comparison of NO
                        <E T="0732">X</E>
                         Inventories Associated With Existing and Revised Budgets for the 2008 8-Hour Ozone Standard
                    </TTITLE>
                    <TDESC>
                        [Tons per summer day] 
                        <SU>a</SU>
                         
                        <SU>b</SU>
                    </TDESC>
                    <BOXHD>
                        <CHED H="1">Inventory source category</CHED>
                        <CHED H="1">Emissions inventory in approved ozone plan</CHED>
                        <CHED H="2">2026</CHED>
                        <CHED H="2">2029</CHED>
                        <CHED H="2">2031</CHED>
                        <CHED H="1">Updated emissions inventory</CHED>
                        <CHED H="2">2026</CHED>
                        <CHED H="2">2029</CHED>
                        <CHED H="2">2031</CHED>
                        <CHED H="1">Net change</CHED>
                        <CHED H="2">2026</CHED>
                        <CHED H="2">2029</CHED>
                        <CHED H="2">2031</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Stationary and Area</ENT>
                        <ENT>32.9</ENT>
                        <ENT>32.3</ENT>
                        <ENT>32.0</ENT>
                        <ENT>23.4</ENT>
                        <ENT>22.3</ENT>
                        <ENT>20.4</ENT>
                        <ENT>−9.5</ENT>
                        <ENT>−10.0</ENT>
                        <ENT>−11.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">On-road</ENT>
                        <ENT>50.4</ENT>
                        <ENT>46.7</ENT>
                        <ENT>45.1</ENT>
                        <ENT>41.1</ENT>
                        <ENT>38.4</ENT>
                        <ENT>37.5</ENT>
                        <ENT>−9.3</ENT>
                        <ENT>−8.3</ENT>
                        <ENT>−7.6</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Non-road</ENT>
                        <ENT>59.7</ENT>
                        <ENT>52.1</ENT>
                        <ENT>48.0</ENT>
                        <ENT>68.0</ENT>
                        <ENT>61.0</ENT>
                        <ENT>57.3</ENT>
                        <ENT>8.3</ENT>
                        <ENT>8.9</ENT>
                        <ENT>9.3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Totals</ENT>
                        <ENT>143.0</ENT>
                        <ENT>131.1</ENT>
                        <ENT>125.1</ENT>
                        <ENT>132.5</ENT>
                        <ENT>121.7</ENT>
                        <ENT>115.2</ENT>
                        <ENT>−10.5</ENT>
                        <ENT>−9.4</ENT>
                        <ENT>−9.9</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>a</SU>
                         For net change, a negative number indicates a reduction in emissions and a positive number indicates an increase in emissions relative to the corresponding figure in the 2016 SJV Ozone SIP. Because of rounding conventions, totals may not reflect individual subcategories.
                    </TNOTE>
                    <TNOTE>
                        <SU>b</SU>
                         The emissions shown for the approved ozone plan are from Appendix A, pages A-29 and A-30 of the 2018 SIP Update. The emissions shown for updated on-road mobile source emissions are the sum of the budgets from Table III-1 of the 2026 Valley Ozone Budget Update. The emissions shown for stationary, area, and non-road emissions are from SJVUAPCD's 2022 Plan for the 2015 8-Hour Ozone Standard (adopted December 15, 2022), Appendix B, table B-1.
                    </TNOTE>
                </GPOTABLE>
                <PRTPAGE P="42404"/>
                <GPOTABLE COLS="10" OPTS="L2,nj,i1" CDEF="s50,8,8,8p,8,8,8p,8,8,8">
                    <TTITLE>Table 5—Comparison of VOC Inventories Associated With Existing and Revised Budgets for the 2008 8-Hour Ozone Standard</TTITLE>
                    <TDESC>
                        [Tons per summer day] 
                        <SU>a</SU>
                         
                        <SU>b</SU>
                    </TDESC>
                    <BOXHD>
                        <CHED H="1">Inventory source category</CHED>
                        <CHED H="1">Emissions inventory in approved ozone plan</CHED>
                        <CHED H="2">2026</CHED>
                        <CHED H="2">2029</CHED>
                        <CHED H="2">2031</CHED>
                        <CHED H="1">Updated emissions inventory</CHED>
                        <CHED H="2">2026</CHED>
                        <CHED H="2">2029</CHED>
                        <CHED H="2">2031</CHED>
                        <CHED H="1">Net change</CHED>
                        <CHED H="2">2026</CHED>
                        <CHED H="2">2029</CHED>
                        <CHED H="2">2031</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Stationary and Area</ENT>
                        <ENT>250.4</ENT>
                        <ENT>255.6</ENT>
                        <ENT>259.2</ENT>
                        <ENT>238.4</ENT>
                        <ENT>240.8</ENT>
                        <ENT>243.2</ENT>
                        <ENT>−12.0</ENT>
                        <ENT>−14.8</ENT>
                        <ENT>−16.0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">On-road</ENT>
                        <ENT>21.3</ENT>
                        <ENT>19.5</ENT>
                        <ENT>18.3</ENT>
                        <ENT>19.4</ENT>
                        <ENT>17.1</ENT>
                        <ENT>15.8</ENT>
                        <ENT>−1.9</ENT>
                        <ENT>−2.4</ENT>
                        <ENT>−2.5</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Non-road</ENT>
                        <ENT>28.6</ENT>
                        <ENT>26.9</ENT>
                        <ENT>25.5</ENT>
                        <ENT>39.5</ENT>
                        <ENT>34.2</ENT>
                        <ENT>31.4</ENT>
                        <ENT>10.9</ENT>
                        <ENT>7.3</ENT>
                        <ENT>5.9</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Totals</ENT>
                        <ENT>300.3</ENT>
                        <ENT>302.0</ENT>
                        <ENT>303.0</ENT>
                        <ENT>297.3</ENT>
                        <ENT>292.1</ENT>
                        <ENT>290.4</ENT>
                        <ENT>−3.0</ENT>
                        <ENT>−9.9</ENT>
                        <ENT>−12.6</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>a</SU>
                         For net change, a negative number indicates a reduction in emissions and a positive number indicates an increase in emissions relative to the corresponding figure in the 2016 SJV Ozone SIP. Because of rounding conventions, totals may not reflect individual subcategories.
                    </TNOTE>
                    <TNOTE>
                        <SU>b</SU>
                         The emissions shown for the approved ozone plan are from Appendix A, pages A-27 and A-28 of the 2018 SIP Update. The emissions shown for updated on-road mobile source emissions are the sum of the budgets from Table III-1 of the 2026 Valley Ozone Budget Update. The emissions shown for stationary, area, and non-road emissions are from SJVUAPCD's 2022 Plan for the 2015 8-Hour Ozone Standard (adopted December 15, 2022), Appendix B, table B-2.
                    </TNOTE>
                </GPOTABLE>
                <P>
                    Under our transportation conformity rule, as a general matter, once budgets are approved, they cannot be superseded by revised budgets submitted for the same CAA purpose and the same period of years addressed by the previously approved SIP until the EPA approves the revised budgets as a SIP revision. In other words, as a general matter, such approved budgets cannot be superseded by revised budgets found adequate, but rather only through approval of the revised budgets, unless the EPA specifies otherwise in its approval of a SIP by limiting the duration of the approval to last only until subsequently submitted budgets are found adequate.
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         40 CFR 93.118(e)(1).
                    </P>
                </FTNT>
                <P>
                    In this instance, as noted above, CARB has requested that we limit the duration of our approval of the budgets in the 2026 Valley Ozone Budget Update only until the effective date of the EPA's adequacy finding for any subsequently submitted budgets. Generally, we will consider a State's request to limit an approval of a budget only if the request includes the following elements: 
                    <SU>22</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         67 FR 69141 (November 15, 2002), limiting our prior approval of motor vehicle emissions budgets in certain California SIPs.
                    </P>
                </FTNT>
                <P>• An acknowledgement and explanation as to why the budgets under consideration have become outdated or deficient;</P>
                <P>• A commitment to update the budgets as part of a comprehensive SIP update; and</P>
                <P>• A request that the EPA limit the duration of its approval to the time when new budgets have been found to be adequate for transportation conformity purposes.</P>
                <P>CARB's request includes an explanation for why the budgets have become, or will become, outdated or deficient. In short, CARB has requested that we limit the duration of the approval of the budgets because CARB expects the next version of EMFAC to estimate higher emissions for certain on-road motor vehicle categories and certain areas of the State, necessitating updates to the budgets once the next version of EMFAC is submitted and approved by the EPA.</P>
                <P>If the EPA approves the future EMFAC model, CARB explains that the budgets from the 2026 Valley Ozone Budget Update, for which we are proposing approval in this action, may become outdated and will need to be revised. In addition, CARB states that, without the ability to replace the budgets using the budget adequacy process, the benefits of using the updated data may not be realized for a year or more after the updated SIP (with the future budgets) is submitted, due to the length of the SIP approval process. For the reasons provided above, and in light of CARB's explanation for why the budgets will become outdated and should be replaced upon an adequacy finding for updated budgets, we propose to limit the duration of our approval of the budgets in the 2026 Valley Ozone Budget Update until new budgets have been found adequate. We find that CARB's explanation for limiting the duration of the approval of the budgets is appropriate and provides us with a reasonable basis on which to limit the duration of the approval of the budgets.</P>
                <P>
                    We note that, in relation to the request to limit the duration of approval of the budgets, CARB has not committed to update the budgets as part of a comprehensive SIP update, but as a practical matter, CARB must submit a SIP revision that includes updated demonstrations as well as the updated budgets to meet the adequacy criteria in 40 CFR 93.118(e)(4); 
                    <SU>23</SU>
                    <FTREF/>
                     and thus, we do not need a specific commitment for such a plan at this time.
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         Under 40 CFR 93.118(e)(4), the EPA will not find a budget in a submitted SIP to be adequate unless, among other criteria, the budgets, when considered together with all other emissions sources, are consistent with applicable requirements for RFP and attainment. 40 CFR 93.118(e)(4)(iv).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Proposed Action and Request for Public Comment</HD>
                <P>For the reasons discussed above, the EPA is proposing to approve the revised ozone budgets in California's April 30, 2026 submittal for the SJV area. The revised budgets are shown in table 1 of this document and are based on estimates from California's EMFAC2021 model, with the EPA-approved November 2025 adjustment factors.</P>
                <P>
                    More specifically, under CAA section 110(k)(3), the EPA is proposing to approve the revised VOC and NO
                    <E T="52">X</E>
                     budgets for 2026, 2029, and 2031 for the 2008 8-hour ozone standard because replacement of the existing approved budgets with the revised budgets would not interfere with the approved RFP and attainment demonstrations for the 2008 8-hour ozone standard in the SJV and because emissions changes in non-motor vehicle emissions categories do not change the overall conclusions of the 2016 SJV Ozone SIP.
                </P>
                <P>With respect to the motor vehicle emissions budgets, we are proposing to limit the duration of the approval of the budgets to last only until the effective date of an adequacy finding by the EPA for any subsequently submitted budgets for the same CAA purpose and years. We are doing so at CARB's request consistent with 40 CFR 93.118(e)(1).</P>
                <P>
                    Lastly, if the EPA takes final action to approve the revised budgets as proposed, the San Joaquin Valley MPOs, FHWA, and FTA would have to use the 
                    <PRTPAGE P="42405"/>
                    revised budgets for future transportation conformity determinations.
                </P>
                <P>
                    The EPA is soliciting public comments on the issues discussed in this document. See the 
                    <E T="02">DATES</E>
                     and 
                    <E T="02">ADDRESSES</E>
                     sections of this 
                    <E T="04">Federal Register</E>
                     proposed action for further details. We will consider these comments before taking final action.
                </P>
                <HD SOURCE="HD1">V. Statutory and Executive Order Reviews</HD>
                <P>Under the CAA, the Administrator is required to approve a SIP submission that complies with the provisions of the Act and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, the EPA's role is to approve State choices, provided that they meet the criteria of the CAA. Accordingly, this action merely proposes to approve a State plan as meeting Federal requirements and does not impose additional requirements beyond those imposed by State law. For that reason, this proposed action:</P>
                <P>• Is not a significant regulatory action subject to review by the Office of Management and Budget under Executive Order 12866 (58 FR 51735, October 4, 1993);</P>
                <P>• Is not an Executive Order 14192 (90 FR 9065, February 6, 2025) regulatory action because this action is not significant under Executive Order 12866;</P>
                <P>
                    • Does not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    );
                </P>
                <P>
                    • Is certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    );
                </P>
                <P>• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);</P>
                <P>• Does not have federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);</P>
                <P>• Is not subject to Executive Order 13045 (62 FR 19885, April 23, 1997) because it proposes to approve a State program;</P>
                <P>• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001); and</P>
                <P>• Is not subject to requirements of section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA.</P>
                <P>In addition, the SIP is not approved to apply on any Indian reservation land or in any other area where the EPA or an Indian Tribe has demonstrated that a Tribe has jurisdiction. In those areas of Indian country, the proposed rule does not have Tribal implications and will not impose substantial direct costs on Tribal governments or preempt Tribal law as specified by Executive Order 13175 (65 FR 67249, November 9, 2000).</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 52</HD>
                    <P>Environmental protection, Air pollution control, Incorporation by reference, Intergovernmental relations, Nitrogen oxides, Ozone, Reporting and recordkeeping requirements, Volatile organic compounds.</P>
                </LSTSUB>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        42 U.S.C. 7401 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 26, 2026.</DATED>
                    <NAME>Michael Martucci,</NAME>
                    <TITLE>Acting Regional Administrator, Region 9.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13845 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>91</VOL>
    <NO>130</NO>
    <DATE>Thursday, July 9, 2026</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="42406"/>
                <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 August 10, 2026 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. 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">Animal and Plant Health Inspection Service</HD>
                <P>
                    <E T="03">Title:</E>
                     Endangered Species Regulations and Forfeiture Procedures.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0579-0076.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     The Endangered Species Act of 1973 (16 U.S.C. 1513 
                    <E T="03">et seq.</E>
                    ) directs Federal departments to utilize their authorities under the Act to conserve endangered and threatened species. Section 3 of the Act specifies that the Secretary of Agriculture is authorized to promulgate such regulations as may be appropriate to enforce the Act. The regulations contained in 7 CFR 355 are intended to carry out the provisions of the Endangered Species Act. USDA's Animal and Plant Health Inspection Service (APHIS), Plant Protection and Quarantine (PPQ) program is responsible for implementing these regulations. To enforce the regulations, APHIS will collect information using several forms and activities.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     APHIS will use the following information activities to conserve endangered and threatened species of terrestrial plants: Applications for protected plant permit form PPQ 621, appeals of denial of general permit, marking and notification requirements, notices of arrival form PPQ 368, notices of exportation, validation of documents, waivers of forfeiture procedures by owners of seized property form PPQ 623, claim form PPQ 625, requests for return of property, petitions for remission or mitigation of forfeiture, reports form PPQ 626, and reporting and recordkeeping. Without the collected information, APHIS would not be able to carry out its responsibilities under The Endangered Species Act, and the United States would not be able to fulfill its responsibilities as a signatory to the Convention on International Trade in Endangered Species (CITES) Treaty. The consequences of either would directly impact the protection of endangered plant species around the world.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Business or other for-profit.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     1,097.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Recordkeeping; Reporting: Third-Party; On occasion.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     14,436.
                </P>
                <SIG>
                    <NAME>Rachelle Ragland-Greene,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13813 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">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 August 10, 2026 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. 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.
                    <PRTPAGE P="42407"/>
                </P>
                <HD SOURCE="HD1">Animal and Plant Health Inspection Service</HD>
                <P>
                    <E T="03">Title:</E>
                     Nomination Request Form; Animal Disease Training.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0579-0353.
                </P>
                <P>
                    <E T="03">Summary of Collection:</E>
                     The Animal Health Protection Act of 2002 is the primary Federal law governing the protection of animal health. The law gives the Secretary of Agriculture broad authority to detect, control, eradicate pests or diseases of livestock or poultry. The Animal and Plant Health Inspection Service (APHIS') Veterinary Services (VS) is responsible for administering regulations intended to prevent the introduction of animal diseases into the United States. VS Professional People Training (PPT) provides training on responses to animal disease events, sample collection procedures, and disease mitigation and eradication activities to private veterinarians and State, Tribal, military, international, industry, and university personnel. The courses are designed to prepare participants for activities dealing with a U.S. animal disease incident.
                </P>
                <P>
                    <E T="03">Need and Use of the Information:</E>
                     VS collects information using VS Form 1-5 from private veterinarians as well as State, Tribal, military, international, university, and industry personnel who want to attend PDS animal disease training. PPT requires the applicants' work addresses, work telephone numbers, work email addresses, agency/organization affiliations, supervisors' names and email addresses, and job titles. PPT uses this information to produce participant rosters after participants select courses and during training to encourage ongoing working relationships between course participants. Applicants submit the completed form (Web-based) before the PPT course date. The appropriate APHIS official selects applicants based on the need in their respective States for such trained personnel. VS Form 1-5 is subsequently sent to a PPT Program Specialist for processing.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Business or other for-profit; State, Local or Tribal Government.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     350.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     Reporting: On occasion.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     116.
                </P>
                <SIG>
                    <NAME>Rachelle Ragland-Greene,</NAME>
                    <TITLE>Departmental Information Collection Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13877 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Forest Service</SUBAGY>
                <SUBJECT>West Virginia Resource Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Forest Service, Agriculture (USDA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The West Virginia Resource Advisory Committee (RAC) will hold a public meeting according to the details shown below. The committee is authorized under the Secure Rural Schools and Community Self-Determination Act (the Act) and operates in compliance with the Federal Advisory Committee Act (FACA). The purpose of the committee is to improve collaborative relationships and to provide advice and recommendations to the Forest Service concerning projects and funding consistent with Title II of the Act as well as make recommendations on recreation fee proposals for sites on the Monongahela National Forest, consistent with the Federal Lands Recreation Enhancement Act.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Meetings will be held in-person and virtual on Monday August 3, 2026, from 10 a.m. to 3 p.m., Thursday August 6, 2026, from 10 a.m. to 3 p.m., and Friday August 7, 2026, from 10 a.m. to 3 p.m., Eastern Daylight Time.</P>
                    <P>
                        <E T="03">Written and Oral Comments:</E>
                         Anyone wishing to provide in-person or virtual oral comments must pre-register by 11:59 p.m. (Eastern Daylight Time) on July 30, 2026. Written public comments will be accepted by 11:59 p.m. (Eastern Daylight Time) on July 23, 2026. Comments submitted after this date will be provided by the Forest Service to the committee, but the committee may not have adequate time to consider those comments prior to the meeting.
                    </P>
                    <P>
                        All RAC meetings are subject to cancellation. For status of the meeting prior to attendance, please contact the person listed under F
                        <E T="02">OR FURTHER INFORMATION ADDRESSES:</E>
                         The meeting(s) will be held in-person and virtually in the Monongahela National Forest Headquarters Building, First Floor Conference Room, 200 Sycamore Street, Elkins, West Virginia, 26241. Committee information and meeting details can be found at the following website 
                        <E T="03">https://www.fs.usda.gov/r09/monongahela/working-with-us/committees or</E>
                         by contacting the person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        .
                    </P>
                    <P>
                        <E T="03">Written Comments:</E>
                         Written comments must be sent by email to 
                        <E T="03">kristopher.hennig@usda.gov or</E>
                         via mail (postmarked) to Kristopher Hennig, 200 Sycamore Street, Elkins, WV, 26241. The Forest Service strongly prefers comments be submitted electronically.
                    </P>
                    <P>
                        <E T="03">Oral Comments:</E>
                         Persons or organizations wishing to make oral comments must pre-register by 11:59 p.m. (Eastern Daylight Time) on July 30, 2026, and speakers can only register for one speaking slot. Oral comments must be sent by email to 
                        <E T="03">Kristopher.Hennig@usda.gov</E>
                         or via mail (postmarked) to Kristopher Hennig, 200 Sycamore Street, Elkins, WV 26241.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Cindy Sandeno, Designated Federal Officer, by phone at 304-635-4482 or email at 
                        <E T="03">Cynthia.Sandeno@usda.gov;</E>
                         or Kristopher Hennig, RAC Coordinator by phone at 304-635-4475 or email at 
                        <E T="03">Kristopher.Hennig@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The purpose of the meeting is to:</P>
                <P>1. Provide administrative and Resource Advisory Committee updates;</P>
                <P>2. Hear from Title II project proponents and discuss Title II project proposals;</P>
                <P>3. Make funding recommendations on Title II projects;</P>
                <P>4. Approve meeting minutes;</P>
                <P>5. Other.</P>
                <P>
                    Please contact the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    , by or before the deadline, for all questions related to the meeting. All comments, including names and addresses when provided, are placed in the record and are available for public inspection and copying. The public may inspect comments received upon request.
                </P>
                <P>
                    <E T="03">Meeting Accommodations:</E>
                     If you are a person requiring reasonable accommodation, please make a request in advance for sign language interpreting, assistive listening devices, or other reasonable accommodation. For access to proceedings, please contact the person listed in the section titled 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    . All reasonable accommodation requests are managed on a case-by-case basis.
                </P>
                <P>Equal opportunity practices, in accordance with USDA policies, will be followed in all membership appointments to the committee.</P>
                <P>
                    In accordance with Federal civil rights law and U.S. Department of Agriculture (USDA) civil rights regulations and policies, the USDA, its agencies, offices, employees, and institutions participating in or administering USDA programs are prohibited from discriminating based on race, color, national origin, religion, sex, disability, age, marital status, family/parental status, income derived from a public assistance program, political beliefs, or reprisal or retaliation for prior 
                    <PRTPAGE P="42408"/>
                    civil rights activity, in any program or activity conducted or funded by USDA (not all bases apply to all programs). Remedies and complaint filing deadlines vary by program or incident.
                </P>
                <SIG>
                    <DATED>Dated: June 26, 2026.</DATED>
                    <NAME>Cikena Reid,</NAME>
                    <TITLE>USDA Committee Management Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13838 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3411-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Forest Service</SUBAGY>
                <SUBJECT>Idaho Panhandle Resource Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Forest Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Idaho Panhandle Resource Advisory Committee (RAC) will hold a public meeting according to the details shown below. The committee is authorized under the Secure Rural Schools and Community Self-Determination Act (the Act) and operates in compliance with the Federal Advisory Committee Act (FACA). The purpose of the committee is to improve collaborative relationships and to provide advice and recommendations to the Forest Service concerning projects and funding consistent with Title II of the Act as well as make recommendations on recreation fee proposals for sites on the Idaho Panhandle National Forests, consistent with the Federal Lands Recreation Enhancement Act.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>An in-person and virtual meeting will be held on August 18, 2026, and August 19, 2026, at 9 a.m., Pacific Daylight Time.</P>
                    <P>
                        <E T="03">Written and Oral Comments:</E>
                         Anyone wishing to provide in-person or virtual oral comments must pre-register by 11:59 p.m. Pacific Daylight Time on August 15, 2026. Written public comments will be accepted by 11:59 p.m. Pacific Daylight Time on August 15, 2026. Comments submitted after this date will be provided by the Forest Service to the committee, but the committee may not have adequate time to consider those comments prior to the meeting.
                    </P>
                    <P>
                        All RAC meetings are subject to cancellation. For status of the meeting prior to attendance, please contact the person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        .
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held at the Interagency Natural Resource Center, 3232 West Nursery Road, in Coeur d'Alene, Idaho 83815, and virtually via video conference. Members of the public may participate in the meeting by joining virtually via videoconference at: Microsoft Teams/Meeting </P>
                    <P>
                        <E T="03">ID: https://teams.microsoft.com/meet/260483352953808?p=elFoB3ZtSs4ohMgDR7.</E>
                    </P>
                    <P>
                        <E T="03">Meeting ID:</E>
                         260 483 352 953 808, Passcode: 8PX3N38k or Dial in by phone +1 (202) 650-0123, passcode 396886543# United States, Washington; Phone conference ID: 396 886 543#. Committee information and meeting details can be found at the following website 
                        <E T="03">https://www.fs.usda.gov/r01/idahopanhandle/working-with-us/committees</E>
                         or by contacting the person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        .
                    </P>
                    <P>
                        <E T="03">Written Comments:</E>
                         Written comments must be sent by email to 
                        <E T="03">patrick.lair@usda.gov or</E>
                         via mail (postmarked) to Patrick Lair, Public Affairs Officer, 3232 West Nursery Road, Coeur d'Alene, Idaho 83815. The Forest Service strongly prefers comments to be submitted electronically.
                    </P>
                    <P>
                        <E T="03">Oral Comments:</E>
                         Persons or organizations wishing to make oral comments must pre-register by 11:59 p.m. Pacific Daylight Time, August 15, 2026, and speakers can only register for one speaking slot. Oral comments must be sent by email to 
                        <E T="03">patrick.lair@usda.gov</E>
                         or via mail (postmarked) to Patrick Lair, Public Affairs Officer, 3232 West Nursery Road, Coeur d'Alene, Idaho 83815.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Tim Gilloon, Designated Federal Officer, by phone at (208) 765-7223 or email at 
                        <E T="03">timothy.gilloon@usda.gov</E>
                         or Patrick Lair, RAC Coordinator at (208) 765-7211 or email at 
                        <E T="03">patrick.lair@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The purpose of the meeting is to:</P>
                <P>1. Hear from Title II project proponents and discuss Title II project proposals;</P>
                <P>2. Make funding recommendations on Title II projects;</P>
                <P>3. Approve meeting minutes; and</P>
                <P>4. Schedule the next meeting.</P>
                <P>
                    Please contact the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    , by or before the deadline, for all questions related to the meeting. All comments, including names and addresses when provided, are placed in the record and are available for public inspection and copying. The public may inspect comments received upon request.
                </P>
                <P>
                    <E T="03">Meeting Accommodations:</E>
                     If you are a person requiring reasonable accommodation, please make a request in advance for sign language interpreting, assistive listening devices, or other reasonable accommodation. For access to proceedings, please contact the person listed in the section titled 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    . All reasonable accommodation requests are managed on a case-by-case basis.
                </P>
                <P>Equal opportunity practices, in accordance with USDA policies, will be followed in all membership appointments to the Committee.</P>
                <P>In accordance with Federal civil rights law and U.S. Department of Agriculture (USDA) civil rights regulations and policies, the USDA, its Agencies, offices, employees, and institutions participating in or administering USDA programs are prohibited from discriminating based on race, color, national origin, religion, sex, disability, age, marital status, family/parental status, income derived from a public assistance program, political beliefs, or reprisal or retaliation for prior civil rights activity, in any program or activity conducted or funded by USDA (not all bases apply to all programs). Remedies and complaint filing deadlines vary by program or incident.</P>
                <SIG>
                    <DATED>Dated: June 26, 2026.</DATED>
                    <NAME>Cikena Reid,</NAME>
                    <TITLE>USDA Committee Management Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13836 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3411-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Forest Service</SUBAGY>
                <SUBJECT>Fresno and Madera Resource Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Forest Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Fresno and Madera Resource Advisory Committee (RAC) will hold a public meeting according to the details shown below. The committee is authorized under the Secure Rural Schools and Community Self-Determination Act (the Act) and operates in compliance with the Federal Advisory Committee Act (FACA). The purpose of the committee is to improve collaborative relationships and to provide advice and recommendations to the Forest Service concerning projects and funding consistent with Title II of the Act as well as make recommendations on recreation fee proposals for sites on the Sierra National Forst, consistent with the Federal Lands Recreation Enhancement Act.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>An in person and virtual meeting will be held on August 4, 2026, at 5:30 p.m.-7:30 p.m., Pacific Daylight Time.</P>
                    <P>
                        <E T="03">Written and Oral Comments:</E>
                         Anyone wishing to provide in-person or virtual 
                        <PRTPAGE P="42409"/>
                        oral comments must pre-register by 11:59 p.m. (Pacific Daylight Time) on July 30, 2026. Written public comments will be accepted by 11:59 p.m. (Pacific Daylight Time) on July 30, 2026. Comments submitted after this date will be provided to the Agency, but the Committee may not have adequate time to consider those comments prior to the meeting.
                    </P>
                    <P>
                        All RAC meetings are subject to cancellation. For status of the meeting prior to attendance, please contact the person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        .
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The meeting will be held at Sierra National Forest Supervisor's Office, located at 1600 Tollhouse Road, Clovis, California 96311 and virtually via telephone and/or video conference. Members of the public may participate in the meeting by joining virtually via videoconference at: Microsoft Teams/Meeting ID: 265 918 253 3760, Passcode: ko7tJ9qf, or Dial in by phone +1 (323) 886-7051, 492128091# United States, Los Angeles; Phone conference ID: 492 128 091#. Committee information and meeting details can be found at the following website 
                        <E T="03">https://nfs.fs2c.usda.gov/r05/sierra/events/fresno-and-madera-resource-advisory-committee-meeting</E>
                         by contacting the person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        .
                    </P>
                    <P>
                        <E T="03">Written Comments:</E>
                         Written comments must be sent by email to
                        <E T="03"> lily.nieves@usda.gov</E>
                         via mail (postmarked) to Lily Nieves, RAC Coordinator, 
                        <E T="03">1600 Tollhouse Road, Clovis, California 93611.</E>
                         The Forest Service strongly prefers comments to be submitted electronically.
                    </P>
                    <P>
                        <E T="03">Oral Comments:</E>
                         Persons or organizations wishing to make oral comments must pre-register by 11:59 p.m. Daylight Standard Time, July 30, 2026, and speakers can only register for one speaking slot. Oral comments must be sent by email to 
                        <E T="03">lily.nieves@usda.gov</E>
                         or via mail (postmarked) to Lily Nieves, RAC Coordinator, 
                        <E T="03">1600 Tollhouse Road, Clovis, California 93611.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kim Sorini-Wilson, Designated Federal Officer (DFO), by phone at: 559-365-1497 or by email at 
                        <E T="03">kim.sorini@usda.gov,</E>
                         or contact Lily Nieves, RAC Coordinator, at 559-288-9384 or by email at 
                        <E T="03">lily.nieves@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The purpose of the meeting is to:</P>
                <P>1. Discuss Title II project proposals;</P>
                <P>2. Make funding recommendations on Title II projects;</P>
                <P>3. Approve meeting minutes;</P>
                <P>4. Schedule the next meeting</P>
                <P>
                    Please contact the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    , by or before the deadline, for all questions related to the meeting. All comments, including names and addresses when provided, are placed in the record and are available for public inspection and copying. The public may inspect comments received upon request.
                </P>
                <P>
                    <E T="03">Meeting Accommodations:</E>
                     If you are a person requiring reasonable accommodation, please make a request in advance for sign language interpreting, assistive listening devices, or other reasonable accommodation. For access to proceedings, please contact the person listed in the section titled 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    . All reasonable accommodation requests are managed on a case-by-case basis.
                </P>
                <P>Equal opportunity practices, in accordance with USDA policies, will be followed in all membership appointments to the Committee.</P>
                <P>In accordance with Federal civil rights law and U.S. Department of Agriculture (USDA) civil rights regulations and policies, the USDA, its Agencies, offices, employees, and institutions participating in or administering USDA programs are prohibited from discriminating based on race, color, national origin, religion, sex, disability, age, marital status, family/parental status, income derived from a public assistance program, political beliefs, or reprisal or retaliation for prior civil rights activity, in any program or activity conducted or funded by USDA (not all bases apply to all programs). Remedies and complaint filing deadlines vary by program or incident.</P>
                <SIG>
                    <DATED>Dated: June 26, 2026.</DATED>
                    <NAME>Cikena Reid,</NAME>
                    <TITLE>USDA Committee Management Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13837 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3411-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Forest Service</SUBAGY>
                <SUBJECT>Yavapai Resource Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Forest Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Yavapai Resource Advisory Committee (RAC) will hold a public meeting according to the details shown below. The committee is authorized under the Secure Rural Schools and Community Self-Determination Act (the Act) and operates in compliance with the Federal Advisory Committee Act (FACA). The purpose of the committee is to improve collaborative relationships and to provide advice and recommendations to the Forest Service concerning projects and funding consistent with Title II of the Act as well as make recommendations on recreation fee proposals for sites on the Prescott National Forest, consistent with the Federal Lands Recreation Enhancement Act.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>An in person and virtual meeting will be held on August 11, 2026 at 9 a.m. Mountain Standard Time.</P>
                    <P>
                        <E T="03">Written and Oral Comments:</E>
                         Anyone wishing to provide in-person or virtual oral comments must pre-register by 5 p.m. Mountain Standard Time on August 9, 2026. Written public comments will be accepted by 5p.m. Mountain Standard Time August 9, 2026. Comments submitted after this date will be provided by the Forest Service to the committee, but the committee may not have adequate time to consider those comments prior to the meeting.
                    </P>
                    <P>
                        All RAC meetings are subject to cancellation. For status of the meeting prior to attendance, please contact the person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        .
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held at the Prescott Fire Center at 2400 Melville Road, Prescott, AZ, 86301 and virtually via telephone and/or video conference. Members of the public may participate in the meeting by joining virtually via videoconference at: Microsoft Teams meeting.</P>
                    <P>
                        <E T="03">Join: https://teams.microsoft.com/meet/223986069403502?p=JyszUm6ZkoUdpqOZnj</E>
                         Meeting ID: 223 986 069 403 502 Passcode: eV6aS9Nn or Dial in by phone +1 (202) 650-0123, United States, Washington; Phone conference ID: 396 907 175#. Committee information and meeting details can be found at the following website 
                        <E T="03">https://www.fs.usda.gov/r03/prescott/working-with-us/committees</E>
                         or by contacting the person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        .
                    </P>
                    <P>
                        <E T="03">Written Comments:</E>
                         Written comments must be sent by email to 
                        <E T="03">rebekah.blakley@usda.gov or</E>
                         via mail (postmarked) to Rebekah Blakley, Yavapai RAC Coordinator, 735 N. Highway 89, Chino Valley, AZ, 86323. The Forest Service strongly prefers comments to be submitted electronically.
                    </P>
                    <P>
                        <E T="03">Oral Comments:</E>
                         Persons or organizations wishing to make oral comments must pre-register by 5:00 p.m. MST on August 9, 2026 and speakers can only register for one speaking slot. Oral comments must be sent by email to 
                        <E T="03">rebekah.blakley@usda.gov</E>
                         or via mail (postmarked) to Rebekah Blakley, Yavapai RAC 
                        <PRTPAGE P="42410"/>
                        Coordinator, 735 N. Highway 89, Chino Valley, AZ, 86323.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ashley Hom, Designated Federal Officer (DFO), by phone at (719) 239-1139 or by email at 
                        <E T="03">ashley.hom@usda.gov</E>
                         or Rebekah Blakley, Yavapai RAC Coordinator at (928) 777-2218 or by email at 
                        <E T="03">rebekah.blakley@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The purpose of the meeting is to:</P>
                <P>1. REA 101 Training;</P>
                <P>2. Hear Recreation Fee Proposals; and</P>
                <P>3. Vote on Recreation Fee Proposals.</P>
                <P>
                    Please contact the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    , by or before the deadline, for all questions related to the meeting. All comments, including names and addresses when provided, are placed in the record and are available for public inspection and copying. The public may inspect comments received upon request.
                </P>
                <P>
                    <E T="03">Meeting Accommodations:</E>
                     If you are a person requiring reasonable accommodation, please make a request in advance for sign language interpreting, assistive listening devices, or other reasonable accommodation. For access to proceedings, please contact the person listed in the section titled 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    . All reasonable accommodation requests are managed on a case-by-case basis.
                </P>
                <P>Equal opportunity practices, in accordance with USDA policies, will be followed in all membership appointments to the Committee.</P>
                <P>In accordance with Federal civil rights law and U.S. Department of Agriculture (USDA) civil rights regulations and policies, the USDA, its Agencies, offices, employees, and institutions participating in or administering USDA programs are prohibited from discriminating based on race, color, national origin, religion, sex, disability, age, marital status, family/parental status, income derived from a public assistance program, political beliefs, or reprisal or retaliation for prior civil rights activity, in any program or activity conducted or funded by USDA (not all bases apply to all programs). Remedies and complaint filing deadlines vary by program or incident.</P>
                <SIG>
                    <DATED>Dated: June 30, 2026.</DATED>
                    <NAME>Cikena Reid,</NAME>
                    <TITLE>USDA Committee Management Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13832 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3411-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
                <DEPDOC>[S-343-2026]</DEPDOC>
                <SUBJECT>Foreign-Trade Zone 155; Application for Subzone; Kerrville Public Utility Board Public Facility Corporation; Garwood, Texas</SUBJECT>
                <P>An application has been submitted to the Foreign-Trade Zones (FTZ) Board by the Calhoun-Victoria Foreign-Trade Zone, Inc., grantee of FTZ 155, requesting subzone status for the facility of Kerrville Public Utility Board Public Facility Corporation, located in Garwood, Texas. The application was submitted pursuant to the provisions of the Foreign-Trade Zones Act, as amended (19 U.S.C. 81a-81u), and the regulations of the FTZ Board (15 CFR part 400). It was formally docketed on July 6, 2026.</P>
                <P>The proposed subzone (50.87 acres) is located at 3241 Highway 90 Alt, Garwood, Texas. No authorization for production activity has been requested at this time. The proposed subzone would be subject to the existing activation limit of FTZ 155.</P>
                <P>In accordance with the FTZ Board's regulations, Camille Evans of the FTZ Staff is designated examiner to review the application and make recommendations to the Executive Secretary.</P>
                <P>
                    Public comment is invited from interested parties. Submissions shall be addressed to the FTZ Board's Executive Secretary and sent to: 
                    <E T="03">ftz@trade.gov.</E>
                     The closing period for their receipt is August 18, 2026. Rebuttal comments in response to material submitted during the foregoing period may be submitted through September 2, 2026.
                </P>
                <P>
                    A copy of the application will be available for public inspection in the “Online FTZ Information Section” section of the FTZ Board's website, which is accessible via 
                    <E T="03">www.trade.gov/ftz.</E>
                </P>
                <P>
                    For further information, contact Camille Evans at 
                    <E T="03">Camille.Evans@trade.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Elizabeth Whiteman,</NAME>
                    <TITLE>Executive Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13893 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
                <DEPDOC>[B-82-2026]</DEPDOC>
                <SUBJECT>Foreign-Trade Zone 61; Application for Subzone; Sonnell Realty IV, LLC; Bayamón, Puerto Rico</SUBJECT>
                <P>An application has been submitted to the Foreign-Trade Zones (FTZ) Board by the Department of Economic Development and Commerce, grantee of FTZ 61, requesting subzone status for the facility of Sonnell Realty IV, LLC, located in Bayamón, Puerto Rico. The application was submitted pursuant to the provisions of the Foreign-Trade Zones Act, as amended (19 U.S.C. 81a-81u), and the regulations of the FTZ Board (15 CFR part 400). It was formally docketed on July 6, 2026.</P>
                <P>The proposed subzone (11.9 acres) is located at Road PR-2 Km 15.9, Corujo Industrial Sector, Hato Tejas Ward, Bayamón, Puerto Rico. No authorization for production activity has been requested at this time.</P>
                <P>In accordance with the FTZ Board's regulations, Camille Evans of the FTZ Staff is designated examiner to review the application and make recommendations to the FTZ Board.</P>
                <P>
                    Public comment is invited from interested parties. Submissions shall be addressed to the FTZ Board's Executive Secretary and sent to: 
                    <E T="03">ftz@trade.gov.</E>
                     The closing period for their receipt is August 18, 2026. Rebuttal comments in response to material submitted during the foregoing period may be submitted through September 2, 2026.
                </P>
                <P>
                    A copy of the application will be available for public inspection in the “Online FTZ Information Section” section of the FTZ Board's website, which is accessible via 
                    <E T="03">www.trade.gov/ftz.</E>
                </P>
                <P>
                    For further information, contact Camille Evans at 
                    <E T="03">Camille.Evans@trade.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Elizabeth Whiteman,</NAME>
                    <TITLE>Executive Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13894 Filed 7-8-26; 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>
                <SUBJECT>Initiation of Antidumping and Countervailing Duty Administrative Reviews</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Enforcement and Compliance, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <SUM>
                    <PRTPAGE P="42411"/>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of Commerce (Commerce) has received requests to conduct administrative reviews of various antidumping duty (AD) and countervailing duty (CVD) orders with May anniversary dates. In accordance with Commerce's regulations, we are initiating those administrative reviews.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 9, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Brenda E. Brown, AD/CVD Operations, Customs Liaison Unit, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-4735.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>Commerce has received timely requests, in accordance with 19 CFR 351.213(b), for administrative reviews of various AD and CVD orders with May anniversary dates. All deadlines for the submission of various types of information, certifications, comments, or actions by Commerce discussed below refer to the number of calendar days from the applicable starting time.</P>
                <HD SOURCE="HD1">Respondent Selection</HD>
                <P>
                    In the event that Commerce limits the number of respondents for individual examination for administrative reviews initiated pursuant to requests made for the orders identified below, Commerce intends to select respondents based either on U.S. Customs and Border Protection (CBP) data for U.S. imports during the period of review (POR) or questionnaires in which we request the quantity and value (Q&amp;V) of sales, shipments, or exports during the POR. Where Commerce selects respondents based on CBP data, we intend to place the CBP data on the record within five days of publication of the initiation notice. Where Commerce selects respondents based on Q&amp;V data, Commerce intends to place the Q&amp;V questionnaire on the record of the review within five days of publication of the initiation notice. In either case, we intend to make our respondent selection decision within 35 days of the 
                    <E T="04">Federal Register</E>
                     publication of the initiation notice. Comments regarding the CBP data (and/or Q&amp;V data (where applicable)) and respondent selection should be submitted within seven days after the placement of the CBP data/submission of the Q&amp;V data on the record of the review. Parties wishing to submit rebuttal comments should submit those comments within five days after the deadline for the initial comments.
                </P>
                <P>
                    In the event that Commerce decides it is necessary to limit individual examination of respondents and conduct respondent selection under section 777A(c)(2) of the Tariff Act of 1930, as amended (the Act), the following guidelines regarding collapsing of companies for purposes of respondent selection will apply. In general, Commerce has found that determinations concerning whether particular companies should be “collapsed” (
                    <E T="03">e.g.,</E>
                     treated as a single entity for purposes of calculating AD rates) require a substantial amount of detailed information and analysis, which often require follow-up questions and analysis. Accordingly, Commerce will not conduct collapsing analyses at the respondent selection phase of the review and will not collapse companies at the respondent selection phase unless there has been a determination to collapse certain companies in a previous segment of the AD proceeding (
                    <E T="03">e.g.,</E>
                     investigation, administrative review, new shipper review, or changed circumstances review). For any company subject to the review, if Commerce determined, or continued to treat, that company as collapsed with others, Commerce will assume that such companies continue to operate in the same manner and will collapse them for respondent selection purposes. Otherwise, Commerce will not collapse companies for purposes of respondent selection.
                </P>
                <P>
                    <E T="03">Parties are requested to:</E>
                     (a) identify which companies subject to review previously were collapsed, and (b) provide a citation to the proceeding in which they were collapsed. Further, if companies are requested to complete the Q&amp;V questionnaire for purposes of respondent selection, in general, each company must report volume and value data separately for itself. Parties should not include data for any other party, even if they believe they should be treated as a single entity with that other party. If a company was collapsed with another company or companies in the most recently completed segment of the proceeding where Commerce considered collapsing that entity, complete Q&amp;V data for that collapsed entity must be submitted.
                </P>
                <HD SOURCE="HD1">Notice of No Sales</HD>
                <P>
                    With respect to AD administrative reviews, we intend to rescind the review where there are no suspended entries for a company or entity under review and/or where there are no suspended entries under the company-specific case number for that company or entity. Where there may be suspended entries, if a producer or exporter named in this notice of initiation had no exports, sales, or entries during the POR, it may notify Commerce of this fact within 30 days of publication of this initiation notice in the 
                    <E T="04">Federal Register</E>
                     for Commerce to consider how to treat suspended entries under that producer's or exporter's company-specific case number.
                </P>
                <HD SOURCE="HD1">Deadline for Withdrawal of Request for Administrative Review</HD>
                <P>Pursuant to 19 CFR 351.213(d)(1), a party that has requested a review may withdraw that request within 90 days of the date of publication of the notice of initiation of the requested review. The regulation provides that Commerce may extend this time if it is reasonable to do so. Determinations by Commerce to extend the 90-day deadline will be made on a case-by-case basis.</P>
                <HD SOURCE="HD1">Deadline for Particular Market Situation Allegation</HD>
                <P>
                    Section 504 of the Trade Preferences Extension Act of 2015 amended the Act by adding the concept of a particular market situation (PMS) for purposes of constructed value under section 773(e) of the Act.
                    <SU>1</SU>
                    <FTREF/>
                     Section 773(e) of the Act states that “if a particular market situation exists such that the cost of materials and fabrication or other processing of any kind does not accurately reflect the cost of production in the ordinary course of trade, the administering authority may use another calculation methodology under this subtitle or any other calculation methodology.” When an interested party submits a PMS allegation pursuant to section 773(e) of the Act, Commerce will respond to such a submission consistent with 19 CFR 351.301(c)(2)(v). If Commerce finds that a PMS exists under section 773(e) of the Act, then it will modify its dumping calculations appropriately.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         Trade Preferences Extension Act of 2015, Public Law 114-27, 129 Stat. 362 (2015).
                    </P>
                </FTNT>
                <P>
                    Neither section 773(e) of the Act nor 19 CFR 351.301(c)(2)(v) set a deadline for the submission of PMS allegations and supporting factual information. However, in order to administer section 773(e) of the Act, Commerce must receive PMS allegations and supporting factual information with enough time to consider the submission. Thus, should an interested party wish to submit a PMS allegation and supporting new factual information pursuant to section 773(e) of the Act, it must do so no later than 20 days after submission of initial 
                    <PRTPAGE P="42412"/>
                    responses to section D of the questionnaire.
                </P>
                <HD SOURCE="HD1">Separate Rates</HD>
                <P>In proceedings involving non-market economy (NME) countries, Commerce begins with a rebuttable presumption that all companies within the country are subject to government control and, thus, should be assigned a single AD deposit rate. It is Commerce's policy to assign all exporters of merchandise subject to an administrative review in an NME country this single rate unless an exporter can demonstrate that it is sufficiently independent so as to be entitled to a separate rate.</P>
                <P>
                    To establish whether a firm is sufficiently independent from government control of its export activities to be entitled to a separate rate, Commerce analyzes each entity exporting the subject merchandise. In accordance with the separate rates criteria, Commerce assigns separate rates to companies in NME cases only if respondents can demonstrate the absence of both 
                    <E T="03">de jure</E>
                     and 
                    <E T="03">de facto</E>
                     government control over export activities.
                </P>
                <P>All firms listed below that wish to qualify for separate rate status in the administrative reviews involving NME countries must complete, as appropriate, either a Separate Rate Application or Certification, as described below. In addition, all firms that wish to qualify for separate rate status in the administrative reviews of AD orders in which a Q&amp;V questionnaire is issued must complete, as appropriate, either a Separate Rate Application or Certification, and respond to the Q&amp;V questionnaire.</P>
                <P>
                    For these administrative reviews, in order to demonstrate separate rate eligibility, Commerce requires entities for whom a review was requested, that were assigned a separate rate in the most recent segment of this proceeding in which they participated, to certify that they continue to meet the criteria for obtaining a separate rate. The Separate Rate Certification form will be available on Commerce's website at 
                    <E T="03">https://www.trade.gov/non-market-economy-separate-rate-applications-and-certifications</E>
                     on the date of publication of this 
                    <E T="04">Federal Register</E>
                     notice. In responding to the certification, please follow the “Instructions for Filing the Certification” in the Separate Rate Certification. Separate Rate Certifications are due to Commerce no later than 14 calendar days after publication of this 
                    <E T="04">Federal Register</E>
                     notice. In addition to filing a Separate Rate Certification with Commerce no later than 14 calendar days after publication of this 
                    <E T="04">Federal Register</E>
                     notice. The deadline and requirement for submitting a Separate Rate Certification applies equally to NME-owned firms, wholly foreign-owned firms, and foreign sellers who purchase and export subject merchandise to the United States.
                </P>
                <P>
                    Entities that currently do not have a separate rate from a completed segment of the proceeding 
                    <SU>2</SU>
                    <FTREF/>
                     should timely file a Separate Rate Application to demonstrate eligibility for a separate rate in this proceeding. In addition, companies that received a separate rate in a completed segment of the proceeding that have subsequently made changes, including, but not limited to, changes to corporate structure, acquisitions of new companies or facilities, or changes to their official company name,
                    <SU>3</SU>
                    <FTREF/>
                     should timely file a Separate Rate Application to demonstrate eligibility for a separate rate in this proceeding. The Separate Rate Application will be available on Commerce's website at 
                    <E T="03">https://www.trade.gov/non-market-economy-separate-rate-applications-and-certifications</E>
                     on the date of publication of this 
                    <E T="04">Federal Register</E>
                     notice. In responding to the Separate Rate Application, refer to the instructions contained in the application. Separate Rate Applications are due to Commerce no later than 14 calendar days after publication of this 
                    <E T="04">Federal Register</E>
                     notice. The deadline and requirement for submitting a Separate Rate Application applies equally to NME-owned firms, wholly foreign-owned firms, and foreign sellers that purchase and export subject merchandise to the United States.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Such entities include entities that have not participated in the proceeding, entities that were preliminarily granted a separate rate in any currently incomplete segment of the proceeding (
                        <E T="03">e.g.,</E>
                         an ongoing administrative review, new shipper review, 
                        <E T="03">etc.</E>
                        ) and entities that lost their separate rate in the most recently completed segment of the proceeding in which they participated.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Only changes to the official company name, rather than trade names, need to be addressed via a Separate Rate Application. Information regarding new trade names may be submitted via a Separate Rate Certification.
                    </P>
                </FTNT>
                <P>Exporters and producers must file a timely Separate Rate Application or Certification if they want to be considered for individual examination. Furthermore, exporters and producers who submit a Separate Rate Application or Certification and subsequently are selected as mandatory respondents will no longer be eligible for separate rate status unless they respond to all parts of the questionnaire as mandatory respondents.</P>
                <HD SOURCE="HD1">Certification Eligibility</HD>
                <P>Commerce may establish a certification process for companies whose exports to the United States could contain both subject and non-subject merchandise. Companies under review that were deemed to not be eligible to participate in the certification program of that proceeding may submit a Certification Eligibility Application to establish that they maintain the necessary systems to track their sales to the United States of subject and non-subject goods.</P>
                <P>
                    All firms listed below that are not currently eligible to certify but wish to establish certification eligibility are required to submit a Certification Eligibility Application. The Certification Eligibility Application will be available on Commerce's website at 
                    <E T="03">https://www.trade.gov/sites/default/files/2026-02/Certification-Eligibility-Application.pdf?v=1777492320626.</E>
                     Certification Eligibility Applications must be filed according to Commerce's regulations and are due to Commerce no later than 30 calendar days after the publication of the 
                    <E T="04">Federal Register</E>
                     notice.
                </P>
                <P>Exporters and producers that are not currently eligible to certify, who submit a Certification Eligibility Application, and are subsequently selected as mandatory respondents must respond to all parts of the questionnaire as mandatory respondents for Commerce to consider their Certification Eligibility Application.</P>
                <HD SOURCE="HD1">Initiation of Reviews</HD>
                <P>In accordance with 19 CFR 351.221(c)(1)(i), we are initiating administrative reviews of the following AD and CVD orders and findings. We intend to issue the final results of these reviews not later than May 31, 2027.</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s200,15">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Period to be
                            <LI>reviewed</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">BELGIUM: Certain Carbon and Alloy Steel Cut-To-Length Plate, A-423-812</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Industeel Belgium S.A.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42413"/>
                        <ENT I="03" O="xl">Nialco SA.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">NLMK Clabecq S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">NLMK Dansteel A.S</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">NLMK La Louviere S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">NLMK Manage Steel Center S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">NLMK Plate Sales S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">NLMK Sales Europe S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            BRAZIL: Common Alloy Aluminum Sheet,
                            <SU>4</SU>
                             A-351-854
                        </ENT>
                        <ENT>4/1/25-3/31/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRAZIL: Ferrosilicon, A-351-860</ENT>
                        <ENT>11/6/24-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Bozel Brasil S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Companhia De Ferro Ligas Da Bahia—FERBASA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Granha Ligas Ltda.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Inonibras Inoculantes E Ferro Ligas</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Libra Ligas Do Brasil S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ligas de Aluminio S.A.—LIASA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Minasligas S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nexus Manganes S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nova Era Silicon</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Rima Industrial S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Rotavi Industrial Ltda.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">CANADA: Large Diameter Welded Pipe, A-122-863</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Acier Profile SBB Inc</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Aciers Lague Steels Inc</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Amdor Inc</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">BPC Services Group</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Bri‐Steel Manufacturing</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">CFI Metal Inc</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Canada Culvert</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Canadian National Steel Corp.; Evraz Inc. NA Canada; Evraz Inc. NA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Canam (St Gedeon)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Cappco Tubular Products Canada Inc</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dominion Pipe &amp; Piling</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Enduro Canada Pipeline Services</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Fi Oilfield Services Canada</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Forterra</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Gchem Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Graham Construction</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Groupe Fordia Inc</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hart Pump Services</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hodgson Custom Rolling</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hyprescon Inc</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Interpipe Inc</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">K K Recycling Services</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kobelt Manufacturing Co</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Labrie Environment</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Les Aciers Sofatec</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lorenz Conveying Products</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Matrix Manufacturing</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">MBI Produits De Forge</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nor Arc</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Peak Drilling Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Pipe &amp; Piling Supplies Ltd.; 1045761 Ontario Ltd.; Spiralco Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Prudential</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shaw Pipe Protection</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tenaris Algoma Tubes Facility</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tenaris Prudential</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Welded Tube of Can Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">France: Certain Carbon and Alloy Steel Cut-To-Length Plate, A-427-828</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dillinger France S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Germany: Certain Carbon and Alloy Steel Cut-To-Length Plate, A-428-844</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">AG der Dillinger Huttenwerke</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GERMANY: Common Alloy Aluminum Sheet, A-428-849</ENT>
                        <ENT>4/1/25-3/31/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            HOMAPAL GmbH 
                            <SU>5</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">GREECE: Large Diameter Welded Pipe, A-484-803</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Corinth Pipeworks Pipe Industry S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            INDIA: Carbon and Alloy Steel Threaded Rod,
                            <SU>6</SU>
                             A-533-887
                        </ENT>
                        <ENT>4/1/25-3/31/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Daksh Fasteners</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shree Luxmi Fasteners</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nishant Steel Industries</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">INDIA: 2,4-Dichlorophenoxyacetic Acid, A-533-922</ENT>
                        <ENT>11/14/24-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Aero Agro Chemical Industries Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Agrow Allied Ventures Pvt Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Atul Limited</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42414"/>
                        <ENT I="03" O="xl">Epigral Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Matangi Industries LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Meghmani Organics Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sharda Cropchem Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shandong Weifang Rainbow Chemical Co., Ltd.; Ningxia Rainbow Chemical Co. Ltd.; Shandong Rainbow Agrosciences Co., Ltd.; Shandong Weifang Rainbow Chemical Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">INDIA: Organic Soybean Meal, A-533-901</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Agrawal Oil &amp; Biocheam</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Alembic Pharmaceuticals Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ark Line Overseas Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Artevet India LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Asa Agrotech Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ashok Oil &amp; Food Products</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Avt Natural Products Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Awl Agri Business Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">B D Edible Oils Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">B One Business House Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Basillia Organics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Bawa Fishmeal &amp; Oil Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Bergwerff Organic India Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Betul Oil Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Bholenath Exporters</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Crest Container Lines Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dahnay Logistics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Danodia Foods Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Deepkiran Foods Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Delight Lifelike Products Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dg Global (Usa) Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Divis Laboratories Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dr. Reddys Laboratories Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ecopure Specialties Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Euroasias Organics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Forin Container Line</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Grs Agritech</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Indev Infra Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Indication Instruments Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Interport Global Logistics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Janatha Fish Meal &amp; Oil Products</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Januz Universal</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jay Keshav Exp. Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kaj Traders</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kalpvraksh Imp. &amp; Exp.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kapiraj Pharmaceuticals Private Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kemin Industries South Asia Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Khanal Foods Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Krishna Corncob Industries</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Laxmi Protein Products Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lophius</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">LT Foods Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lumis Biotech Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lupin Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Makwell Organics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Markship Logistics International LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Mathrua (M Line) Container Logistics</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Noble Industries</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Noble Shipping Pvt. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nurture Aqua Technology Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nutech Biosciences India Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Oceanid Logistics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Om Exim Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Orgonew Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Paprika Oleos (India) Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Patel Retail Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Puretrop Fruits Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">RPM Exim Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Radhakrishna Agro Industries Pvt. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Rayban Organics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Reindeer Organics LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ryder Shipping Lines Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Samruddhi Organic Farm India Pvt. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sar Transport Systems Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sarla Performance Fibers Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Seair Global Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42415"/>
                        <ENT I="03" O="xl">Sealand Shipping</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sethi International</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shre Devaraja Agro Aseptic</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shree Bhagwati Flour and Foods Pvt. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shreeram Fibres India Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shri Sumati Industries Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shri Sumati Oil Industries Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Singh Agritech Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Skyfer Logistic (Del) Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Specialty Indian Food Parks &amp; Exp. Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Suminter India Organics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sun Pharmaceutical Industries Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Teamglobal Logistics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tex Biosciences Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tit-Bit Foods (India) Pvt. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Venkatesh Food Industries</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Viraje Cargo Care Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">WorldWide Logistics (India) Pvt., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">INDIA: Silicomanganese, A-533-823</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Alloys and Metals India</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Maithan Alloys Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shyam Sel and Power Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            INDONESIA: Mattresses,
                            <SU>7</SU>
                             A-560-836
                        </ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">PT. Zinus Global Indonesia</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ITALY: Certain Carbon and Alloy Steel Cut-To-Length Plate, A-475-834</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">F.A.R. Fonderie Acciaierie S.p.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ferriera Valsider SpA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lasertech S.R.L.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Metinvest Trametal SpA.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">NLMK Verona SpA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nuova Carpenteria Odoles S.R.L.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Officine Technosider s.r.l.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Pro Form S.R.L.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Simic S.P.A</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">JAPAN: Diffusion-Annealed, Nickel-Plated Flat-Rolled Steel Products, A-588-869</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Higuchi Manufacturing Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">IHI Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Marubeni-Itochu Steel, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Metal One Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Mitsubishi Materials Trading Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nichias Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nippon Steel Logistics Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nippon Steel Trading Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">NKPlustec Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">NOK Corporation Tokyo, Japan</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Okaya &amp; Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Oneda Electric Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Panasonic Operational Excellence Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Proterial Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sumisho Metalex Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tomiyasu &amp; Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tokyo Metal Resources Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Toyo Kohan Co., Ltd.; Kohan Shoji Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">KAZAKHSTAN: Ferrosilicon, A-834-812</ENT>
                        <ENT>11/6/24-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">ASIA FerroAlloys LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">KazSilicon Metallurgical Combine LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">YDD Corporation LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Eurasian Energy Corporation JSC</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shubarkol Komir JSC</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">TELF AG</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">TNC Kazchrome JSC</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Karaganda Complex Alloys Plant LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">KSP Steel</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MALAYSIA: Mattresses, A-557-818</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Premier High Ventures</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Finory World Trading</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lion YTT World</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Majuan Jaya Trading</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">PI Elemental Resources</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hestart Venture</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">GGC Global</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Winstra Ventures</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MALAYSIA: Dioctyl Terephthalate, A-557-857</ENT>
                        <ENT>11/5/24-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42416"/>
                        <ENT I="03" O="xl">UPC Chemicals (Malaysia) Sdn Bhd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MALAYSIA: Ferrosilicon, A-557-828</ENT>
                        <ENT>11/6/24-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">OM Materials (Sarawak) Sdn. Bhd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">OM Materials (S) Pte Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Pertama Ferroalloys Sdn. Bhd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">MEXICO: Large Residential Washers, A-201-842</ENT>
                        <ENT>2/1/25-1/31/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            LG Electronics Mexicali, S.A. de C.V.
                            <SU>8</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NETHERLANDS: Certain Preserved Mushrooms, A-421-815</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Okechamp B.V.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">OMAN: Polyethylene Terephthalate Resin, A-523-810</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">OCTAL SAOC-FZC</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">POLAND: Certain Preserved Mushrooms, A-455-806</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Okechamp S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">POLAND: Dioctyl Terephthalate, A-455-808</ENT>
                        <ENT>11/5/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Grupa Azoty Zaklady Azotowy</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF KOREA: Carbon and Alloy Steel Wire Rod, A-580-891</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">POSCO International Corporation; POSCO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF KOREA: Certain Carbon and Alloy Steel Cut-To-Length-Plate, A-580-887</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">POSCO International Corporation; POSCO</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF KOREA: Epoxy Resins, A-580-919</ENT>
                        <ENT>11/13/24-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kukdo Chemical Co., Ltd.; Kukdo Finechem Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kumho P&amp;B Chemicals, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF KOREA: Large Diameter Welded Pipe, A-580-897</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">AJU Besteel Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chang Won Bending Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Daiduck Piping Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dongbu Incheon Steel Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dongkuk Steel Mill Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dong Yang Steel Pipe Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">EEW KHPC Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">EEW Korea Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Geumok Tech. Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">GS Global Corp</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hansol Metal Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Histeel Co., Ltd./H Steel Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Husteel Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hyundai RB Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hyundai Steel Company</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hyundai Steel Pipe Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Il Jin Nts Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kiduck Industries Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kukje Steel Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kum Kang Kind. Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kumsoo Connecting Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">LS Metal Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nexteel Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">SeAH Steel Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Seonghwa Industrial Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">SIN‐E B&amp;P Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Steel Flower Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">WELTECH Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF KOREA: Polyester Staple Fiber, A-580-839</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Huvis Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Toray Advanced Materials Korea, Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF TÜRKIYE: Carbon and Alloy Steel Wire Rod, A-489-831</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Diler Dis Ticaret A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF TÜRKIYE: Circular Welded Carbon Steel Pipes and Tubes, A-489-501</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Borusan Birlesik Boru Fabrikalari San ve Tic.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Borusan Gemlik Boru Tesisleri A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Borusan Holding</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Borusan Ihracat Ithalat ve Dagitim A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Borusan Ithicat ve Dagitim A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Borusan Mannesmann Boru Sanayi ve Ticaret A.Ş.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Borusan Mannesmann Yatirim Holding</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Borusman Istikbal Ticaret T.A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Borusan Pipe U.S., Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Cayirova Boru Sanayi ve Ticaret A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Çinar Boru Profil San. Ve Tic. Aş</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Erbosan Erciyas Boru Sanayi ve Ticaret A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kale Bağlanti Teknolojileri San. ve Tic. A.Ş.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Noksel Çelik Boru Sanayi A.Ş</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Toscelik Metal Ticaret A.Ş.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tosçelik Profil Ve Sac Endüstrisi A.Ş.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42417"/>
                        <ENT I="03" O="xl">Tosyali Dis Ticaret A.S</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tubeco Pipe and Steel Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yucel Boru ve Profil Endustrisi A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yucelboru Ihracat Ithalat ve Pazarlama A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF TÜRKIYE: Dioctyl Terephthalate, A-489-852</ENT>
                        <ENT>11/5/24-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">By Petrokimya Sanayi Ve Ticaret A.S</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF TÜRKIYE: Large Diameter Welded Pipe, A-489-833</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Cagil Makina San ve Tic A.S. AKA Cagil Makina A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Çimtaş Boru Imalatiral Ticaret Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Emek Boru Makina Sanayi ve Ticaret A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Erciyas Celik Boru Sanayi A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            HDM Celik Boru Sanayi ve Ticaret A.S.; HDM Spiral Kaynakli Boru A.S.
                            <SU>9</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Mazlum Mangtay Boru Son. Ins. Tar.Urn.San.ve Tic. A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Noksel Celik Boru Sanayi A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ozbal Celik Boru San. Tic. Ve TAAH A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Spirally Welded Steel Pipe Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Toscelik Profil ve Sac End. A.S.
                            <SU>10</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Toscelik Spiral Boru Uretim A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Umran Celik Boru Sanayii A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF TÜRKIYE: Mattresses, A-489-841</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">BRN Yatak Baza Ev Tekstili Ins. San.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">BRN Yatak Baza Ev Tekstili Insaat Sanayi Ticaret A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Metal Matris Sanayi Ticaret A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Mitsan Makina Insaat Tic Ve San AS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yatas Yatak Ve Yorgan San. Tic. AS</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">SOCIALIST REPUBLIC OF VIETNAM: Mattresses, A-552-827</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dong Guan City Sinoshine</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">East Asia (Vietnam) Polymer Company</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ess Asia Manufacturing and Trading</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shang Zhi Vietnam Trading-Producing</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sinoshine Health Technology Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            SOCIALIST REPUBLIC OF VIETNAM: Certain Paper Plates,
                            <SU>11</SU>
                             A-552-839
                        </ENT>
                        <ENT>9/5/24-2/28/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAIWAN: Certain Epoxy Resins, A-583-876</ENT>
                        <ENT>11/13/24-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chang Chun Plastics Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nan Ya Plastics Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAIWAN: Dioctyl Terephthalate, A-583-875</ENT>
                        <ENT>11/5/24-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nan Ya Plastics Corp.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAIWAN: Stilbenic Optical Brightening Agents, A-583-848</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chitec Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shuang Bang Industrial Corp.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Teh Fong Ming International Co., Ltd.; Teh Fong Min International Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            THAILAND: Epoxy Resins,
                            <SU>12</SU>
                             A-549-850
                        </ENT>
                        <ENT>11/13/24-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Aditya Birla Chemicals (Thailand) Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THAILAND: Mattresses, A-549-841</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Honor Home (Laos) Sole Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hyundai Glovis Logistics (Thailand)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Mountpax Company Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nisco (Thailand) Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            THE PEOPLE'S REPUBLIC OF CHINA: Alloy and Certain Carbon Steel Threaded Rod,
                            <SU>13</SU>
                             A-570-104
                        </ENT>
                        <ENT>4/1/25-3/31/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THE PEOPLE'S REPUBLIC OF CHINA: Aluminum Extrusions, A-570-967</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">AD Solutions</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Anji Chang Hong Chain Manufacturing Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Anji Dingze Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Assa Abloy (Zhongshan) Security Technology</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Assa Abloy Entrance Systems Suzhou</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Assa Abloy Global Solutions (Shanghai)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Baolida Window &amp; Door Accessories</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Beauty Sky Technology Co., Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Beijing Hongyi Denon International</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Beijing Kangtengwei International Trade Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Cargo Services Group Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Changchun Tianlong Automotive Components Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chengde Greenlife Home Product Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chengdu Metalware Trading Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chongqing Chaoli Electric Appliance</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chongqing Millison Technologies Inc</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Citic Dicastal Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">CMECH Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Damco China Limited Ningbo Branch</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dezhou Huamei Windows and Doors Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dongguan Kowin Metal Precision Fabrication Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dura Shower Enclosures Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ener Technology Co. Limited</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42418"/>
                        <ENT I="03" O="xl">Ewellix Motion Technologies (Pinghu)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Foshan Kinghorn Machinery Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Foshan Zhongfeixin Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Green &amp; Light Automotive Components</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Guangdong Xiongjin Metal Products</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Guangzhou Valeo Engine Cooling Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hangzhou Douhao Import and Export Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hangzhou Susan I E Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hangzhou Xline Machinery &amp; Equipment Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hebei Jinshi Industrial Metal Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Huzhou Minghua Auto Parts and Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">IKD Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ji'an Bangwei Home Improvement Prod.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jiangxi Fangda Tech Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jiangsu Tongshun Power Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jiangsu Wenhui Steel Engineering</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jianxin Zhao's Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">JOC Machinery Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">KECO Metal Manufacturing (HK) Co., Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lancham International Trade Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Larkcop International Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Liberty Lift Solution Shandong Oilfield Equipment Manufacturing Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lifestyle Metal Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Maxwell China Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Minglei Industry Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Modine Thermal Systems (Changzhou)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nantong Jianghua Machinery Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Allart International Trade Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Best Hardware Products Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Daye Garden Industry Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Dungyi &amp; Yulian Casting Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Harsco Machinery Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Lianda Winch Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Mogb Machinery Import &amp; Export Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Runner Industrial Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Wubian Rubber and Plastic Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Yesheng Precision Technical</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Yongsheng Metal Manufacturing Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Zhenlong Auto Parts Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Oubao Security Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Pan Jack Industrial Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Paslode Fasteners (Shanghai) Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Puhui Home and Leisure Goods Company</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Pxi Auto Components (Suzhou) Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Qingdao Hisense Mould Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Qingdao Sanheshan Precision Casting</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Rainbird Irrigation Equipment Shanghai</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Relux Products Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">SAIC Volkswagen Automotive Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shanghai Homeland Info Tech Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shanghai Hongji Metal Products Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shanghai Shinekin Automotive Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shanghai Zesheng Automotive Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shenzhen Wulup S.C.M. Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shunde Native Produce Import &amp; Export Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sunrise Machinery Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Suzhou Quality Import and Export Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Suzhou Shida Tongtai Automotive Components Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Synergy Architectural Hardware Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Techno Precision (Shen Zhen) Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tianjin Wanda Tyre Group Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">United Precision Casting Development Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Usual Material Group Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Via Asia Supply Chain Management Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Wisdom Electronics (Huizhou) Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Wuxi Bangde Machine Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Wuxi Dongpeng Metal Products Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Wuxi Huaguang Car Parts Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Xiamen Xianghao Trading Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yakima (Najing) Precison Industry Co</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yiwu Oak Forest Import and Export Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yuhuan Huachao Machine Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yuyao Nuohai Metalwork Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42419"/>
                        <ENT I="03" O="xl">Zenith Industry (Shanghai) Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhangqiu Copper and Aluminum Casting</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhaoqing City Zhisheng Door Control</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhejiang Dongfeng Refrigeration Components Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhejiang Rongtai Electric Material Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhongce Rubber Group Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhongnan Aluminum Wheel</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhongshan Domustar Shower Company</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhongnan Industrial Group Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhongshan Huaguan Hardware Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">ZZF Fence Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            THE PEOPLE'S REPUBLIC OF CHINA: Certain Aluminum Foil,
                            <SU>14</SU>
                             A-570-053
                        </ENT>
                        <ENT>4/1/25-3/31/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            THE PEOPLE'S REPUBLIC OF CHINA: Certain Frozen Warmwater Shrimp,
                            <SU>15</SU>
                             A-570-893
                        </ENT>
                        <ENT>2/1/25-1/31/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Allied Pacific Aquatic Products (Zhanjiang) Co., Ltd./Allied Pacific Food (Dalian) Co., Ltd.
                            <SU>16</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Shantou Red Garden Food Processing Co., Ltd./Shantou Red Garden Foodstuff Co., Ltd.
                            <SU>17</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Zhanjiang Guolian Aquatic Products Co., Ltd.
                            <SU>18</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Zhanjiang Regal Integrated Marine Resources Co., Ltd.
                            <SU>19</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THE PEOPLE'S REPUBLIC OF CHINA: Disposable Aluminum Containers, Pans, Trays, and Lids, A-570-170</ENT>
                        <ENT>12/30/24-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Able Ready Packaging Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Foshan Mestaek Packaging Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Guangzhou Huafeng Aluminum Foil Technologies Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Duong Vu Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhangjiagang Kangyuan International Trading Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THE PEOPLE'S REPUBLIC OF CHINA: Non-refillable Steel Cylinders, A-570-126</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Eagle Machinery &amp; Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sanjiang Kai Yuan Co. Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Wuyi Xilinde Machinery Manufacture Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhejiang KIN-SHINE Technology Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THE PEOPLE'S REPUBLIC OF CHINA: Stilbenic Optical Brightening Agents, A-570-972</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Beijing Odyssey Chemical Ind. Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">CIXI Jiangnan Chemical Fiber Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">CSFC Taiwan Enterprise Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dongguan Tangxia Kong Fung</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Guangzhou New Textile Chemical Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hebei Dianchang Chemicals Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jiangsu Glory Chemical Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jinan Subang Fine Chemical Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo New Dragon International</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhejiang Hongda Chemicals Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhejiang Transfar Whyyon Chemical Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">UNITED ARAB EMIRATES: Steel Nails, A-520-804</ENT>
                        <ENT>5/1/25-4/30/26</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Rich Well Steel Industries LLC</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="21">
                            <E T="02">CVD Proceedings</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">BRAZIL: Ferrosilicon, C-351-861</ENT>
                        <ENT>9/10/24-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Bozel Brasil S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Companhia de Ferro Ligas da Bahia-FERBASA; Fundacao Jose Carvalho Foundation 
                            <SU>20</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Granha Ligas LTDA</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Inonibras Inoculantes E Ferro Ligas</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Libra Ligas Do Brasil S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ligas de Aluminio S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Minasligas S.A.; Irmazi Participacoes S.A.; Participacoes SZ Ltd.Centrium</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Empreendimentos Ltda 
                            <SU>21</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nexus Manganes S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nova Era Silicon</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Rima Industrial S.A.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Rotavi Industrial Ltda.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">INDIA: 2,4-Dichlorophenoxyacetic Acid, C-533-923</ENT>
                        <ENT>9/13/24-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Aero Agro Chemical Industries Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Agrow Allied Ventures Pvt. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Atul Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Epigral Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Matangi Industries LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Meghmani Organics Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningxia Rainbow Chemical Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shandong Rainbow Agrosciences Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shandong Weifang Rainbow Chemical Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sharda Cropchem Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">INDIA: Organic Soybean Meal, C-533-902</ENT>
                        <ENT>1/1/25-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">ABC Fruits</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Agrawal Oil &amp; Biocheam</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Alembic Pharmaceuticals Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ark Line Overseas Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42420"/>
                        <ENT I="03" O="xl">Asa Agrotech Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Avt Natural Products Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">B D Edible Oils Private Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">B One Business House Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Basillia Organics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Bergwerff Organic India Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Betul Oil Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Bholenath Exporters</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Continental Carriers Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Crest Container Lines Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dahnay Logistics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Delight Lifelike Products Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dr. Reddys Laboratories Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ecopure Specialties Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Euroasias Organics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Forin Container Line</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Grs Agritech</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Indev Infra Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Interport Global Logistics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jairaj Adi Global Food Products LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Januz Universal</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jay Keshav Exp. Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kaj Traders</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kalpvraksh Imp. &amp; Exp.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kapiraj Pharmaceuticals Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kemin Industries South Asia Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lophius</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">LT Foods Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lupin Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Makwell Organics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Markship Logistics International LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Noble Industries</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Noble Shipping Pvt. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Novel Nutrients Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nurture Aqua Technology Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nutech Biosciences India Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Orgonew Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Paprika Oleos (India) Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Patel Retail Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Pck Agri Ventures Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Puretrop Fruits Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">RPM Exim Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Radhakrishna Agro Industries Pvt. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Reindeer Organics LLP</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ryder Shipping Lines Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Samruddhi Organic Farm India Pvt. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sar Transport Systems Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sealand Shipping</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sethi International</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shree Bhagwati Flour and Foods Pvt. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shreeram Fibres India Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shri Sumati Industries Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shri Sumati Oil Industries Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Singh Agritech Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Specialty Indian Food Parks &amp; Exp. Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Suminter India Organics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sun Pharmaceutical Industries Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Team Global Logistics Pvt., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tex Biosciences Private Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tit-Bit Foods (India) Pvt. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Viraje Cargo Care Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">WWLP Logistics Pvt., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Malaysia: Ferrosilicon, C-557-829</ENT>
                        <ENT>9/10/24-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">OM Materials (S) Pte Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            OM Materials (Sarawak) Sdn Bhd.; OM Materials &amp; Logistics (M) Sdn. Bhd; OM Materials (Samalaju) Sdn. Bhd; OM Engineering Tech (M) Sdn. Bhd.
                            <SU>22</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Pertama Ferroalloys Sdn. Bhd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF KOREA: Carbon and Alloy Steel Cut-To-Length Plate, X-580-888</ENT>
                        <ENT>1/1/25-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            POSCO; POSCO Holdings Inc.; POSCO Future M Co., Ltd.; POSCO Mobility Solution Co., Ltd.; POSCO M-Tech Co., Ltd.; POSCO Nippon Steel RHF Joint Venture Co., Ltd.
                            <SU>23</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            POSCO International Corporation 
                            <SU>24</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF KOREA: Large Diameter Welded Pipe, C-580-898</ENT>
                        <ENT>1/1/25-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">AJU Besteel Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42421"/>
                        <ENT I="03" O="xl">Chang Won Bending Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Daiduck Piping Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dong Yang Steel Pipe Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dongbu Incheon Steel Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dongkuk Coated Metal Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">EEW KHPC Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">EEW Korea Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">GS Global Corp.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hansol Metal Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Histeel Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">H Steel Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Husteel Co., Ltd.
                            <SU>25</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hyundai RB Co., Ltd.; Shinchang Construction Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Hyundai Steel Company 
                            <SU>26</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hyundai Steel Pipe Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Il Jin Nts Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Iljin Nts Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kem Solutions Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kiduck Industries Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kum Kang Kind. Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Kumsoo Connecting Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nexteel Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">POSCO International Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Samkang M&amp;T Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">SeAH Steel Corporation; SeAH Steel Holdings Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Seonghwa Industrial Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">SIN‐E B&amp;P Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Steel Flower Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">WELTECH Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF TÜRKIYE: Large Diameter Welded Pipe, C-489-834</ENT>
                        <ENT>1/1/25-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Cagil Makina San ve Tic A.S. AKA Cagil Makina A.S.Cagil Makina San ve Tic A.S. AKA Cagil Makina A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Çimtaş Boru Imalatiral Ticaret Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Emek Boru Makina Sanayi ve Ticaret A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Erciyas Celik Boru Sanayi A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            HDM Celik Boru Sanayi ve Ticaret A.S.; HDM Spiral Kaynakli Boru A.S.
                            <SU>27</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Mazlum Mangtay Boru Son. Ins. Tar.Urn.San.ve Tic. A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Noksel Celik Boru Sanayi A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ozbal Celik Boru San. Tic. Ve TAAH A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Spirally Welded Steel Pipe Inc.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Toscelik Profil ve Sac End. A.S.
                            <SU>28</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Toscelik Spiral Boru Uretim A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Umran Celik Boru Sanayii A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yurt Cimento Sanayi Ve</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">REPUBLIC OF TÜRKIYE: Large Diameter Welded Pipe, C-489-832</ENT>
                        <ENT>1/1/25-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Diler Dis Ticaret A.S.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAIWAN: Certain Epoxy Resins, C-583-877</ENT>
                        <ENT>9/13/24-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chang Chun Plastics Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nan Ya Plastics Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Guangzhou Hansong Electric Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shaoxing Shunxing Metal Producting</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shenzhen Bendian Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sunny Packaging Group Int. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Suzhou Kezhe E-Commerce Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhongshan Xichuang Electronic Technology</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THE PEOPLE'S REPUBLIC OF CHINA: Aluminum Extrusions, C-570-968</ENT>
                        <ENT>1/1/25-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">AD Solutions</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Anji Chang Hong Chain Manufacturing Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Anji Dingze Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Assa Abloy (Zhongshan) Security Technology</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Assa Abloy Entrance Systems Suzhou</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Assa Abloy Global Solutions (Shanghai)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Baolida Window &amp; Door Accessories</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Beauty Sky Technology Co., Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Beijing Hongyi Denon International</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Beijing Kangtengwei International Trade Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Cargo Services Group Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Changchun Tianlong Automotive Components Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chengde Greenlife Home Product Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chengdu Metalware Trading Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chongqing Chaoli Electric Appliance</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Chongqing Millison Technologies Inc</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Citic Dicastal Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">CMECH Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42422"/>
                        <ENT I="03" O="xl">Damco China Limited Ningbo Branch</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dezhou Huamei Windows and Doors Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dongguan Kowin Metal Precision Fabrication Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dura Shower Enclosures Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ener Technology Co. Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ewellix Motion Technologies (Pinghu)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Foshan Kinghorn Machinery Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Foshan Zhongfeixin Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Green &amp; Light Automotive Components</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Guangdong Xiongjin Metal Products</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Guangzhou Valeo Engine Cooling Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hangzhou Douhao Import and Export Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hangzhou Susan I E Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hangzhou Xline Machinery &amp; Equipment Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hebei Jinshi Industrial Metal Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Huzhou Minghua Auto Parts and Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">IKD Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ji'an Bangwei Home Improvement Prod.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jiangxi Fangda Tech Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jiangsu Tongshun Power Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jiangsu Wenhui Steel Engineering</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jianxin Zhao's Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">JOC Machinery Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">KECO Metal Manufacturing (HK) Co., Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lancham International Trade Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Larkcop International Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Liberty Lift Solution Shandong Oilfield Equipment Manufacturing Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lifestyle Metal Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Maxwell China Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Minglei Industry Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Modine Thermal Systems (Changzhou)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Nantong Jianghua Machinery Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Allart International Trade Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Best Hardware Products Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Daye Garden Industry Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Dungyi &amp; Yulian Casting Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Harsco Machinery Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Lianda Winch Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Mogb Machinery Import &amp; Export Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Runner Industrial Corporation</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Wubian Rubber and Plastic Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Yesheng Precision Technical</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Yongsheng Metal Manufacturing Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Ningbo Zhenlong Auto Parts Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Oubao Security Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Pan Jack Industrial Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Paslode Fasteners (Shanghai) Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Puhui Home and Leisure Goods Company</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Pxi Auto Components (Suzhou) Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Qingdao Hisense Mould Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Qingdao Sanheshan Precision Casting</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Rainbird Irrigation Equipment Shanghai</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Relux Products Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">SAIC Volkswagen Automotive Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shanghai Homeland Info Tech Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shanghai Hongji Metal Products Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shanghai Shinekin Automotive Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shanghai Zesheng Automotive Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shenzhen Wulup S.C.M. Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shunde Native Produce Import &amp; Export Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Sunrise Machinery Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Suzhou Quality Import and Export Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Suzhou Shida Tongtai Automotive Components Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Synergy Architectural Hardware Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Techno Precision (Shen Zhen) Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Tianjin Wanda Tyre Group Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">United Precision Casting Development Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Usual Material Group Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Via Asia Supply Chain Management Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Wisdom Electronics (Huizhou) Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Wuxi Bangde Machine Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Wuxi Dongpeng Metal Products Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Wuxi Huaguang Car Parts Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42423"/>
                        <ENT I="03" O="xl">Xiamen Xianghao Trading Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yakima (Najing) Precison Industry Co</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yiwu Oak Forest Import and Export Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yuhuan Huachao Machine Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Yuyao Nuohai Metalwork Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zenith Industry (Shanghai) Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhangqiu Copper and Aluminum Casting</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhaoqing City Zhisheng Door Control</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhejiang Dongfeng Refrigeration Components Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhejiang Rongtai Electric Material Co., Ltd</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhongce Rubber Group Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhongnan Aluminum Wheel</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhongshan Domustar Shower Company</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhongnan Industrial Group Limited</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhongshan Huaguan Hardware Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">ZZF Fence Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THE PEOPLE'S REPUBLIC OF CHINA: Certain Chassis and Subassemblies Thereof, C-570-136</ENT>
                        <ENT>1/1/25-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">CIE Manufacturing (Canada), Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">SinoTrailers</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Qingdao CIMC Special Vehicles Co., Ltd.; Dongguan CIMC Vehicle Co., Ltd.;</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">CIMC Vehicles (Group) Co., Ltd.; Shenzhen CIMC Vehicle Co., Ltd.;</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhumadian CIMC Huajun Casting Co., Ltd.; China International Marine</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Containers (Group) Co., Ltd.; Liangshan CIMC Dongyue Vehicles Co., Ltd.;</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shandong Wanshida Special Vehicle Manufacturing Co., Ltd.; Yangzhou CIMC Tonghua Special Vehicles Co., Ltd.; Zhumadian CIMC Huajun Vehicle Co., Ltd.;</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Gansu CIMC Huajun Vehicles Co., Ltd.; CIMC Vehicles (Liaoning) Co., Ltd.; Zhumadian CIMC Wanjia Axle Co., Ltd.
                            <SU>29</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            THE PEOPLE'S REPUBLIC OF CHINA: Certain Corrosion Inhibitors,
                            <SU>30</SU>
                             C-570-123
                        </ENT>
                        <ENT>1/1/25-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THE PEOPLE'S REPUBLIC OF CHINA: Disposable Aluminum Containers, Pans, Trays, and Lids, C-570-171</ENT>
                        <ENT>10/28/24-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Able Ready Packaging Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Foshan Mestaek Packaging Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Guangzhou Huafeng Aluminum Foil Technologies Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Duong Vu Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhangjiagang Kangyuan International Trading Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhangjiagang Auto Well Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Jiangsu Greensource Health Aluminum Foil Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THE PEOPLE'S REPUBLIC OF CHINA: Mattresses, C-570-128</ENT>
                        <ENT>1/1/25-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dongguan Fengyue Trading Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dongguan Jicheng Trading Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dongguan Qianwei Trading Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Dongguan Wanluyi Trading Co. Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Hangzhou Golden Wheat Technology Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Lo Ah Chong and Company</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shenzhen BJT Technology Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shenzhen Top Commerce Trading Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shenzhen Weisiying Trading Co., Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Shenzhen Yuehailong Technology Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">Zhejiang Meili High Technology Co.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">THE PEOPLE'S REPUBLIC OF CHINA: 2,4-Dichlorophenoxyacetic Acid, C-570-161</ENT>
                        <ENT>9/13/24-12/31/25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">
                            Jiangxi Tianyu Chemical Co., Ltd.
                            <SU>31</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03" O="xl">ADAMA Ltd.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            THE PEOPLE'S REPUBLIC OF CHINA: Carbon and Alloy Steel Threaded Rod,
                            <SU>32</SU>
                             C-570-105
                        </ENT>
                        <ENT>1/1/25-12/31/25</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Suspension Agreements Period To Be Reviewed</HD>
                <P>
                    None.
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Commerce published an incorrect POR in the prior initiation notice associated with this review and hereby corrects the POR to reflect the actual period for this administrative review. 
                        <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews,</E>
                         91 FR 32928 (June 2, 2026).
                    </P>
                    <P>
                        <SU>5</SU>
                         Commerce inadvertently omitted this company from the initiation notice published on June 2, 2026 (91 FR 32928). Inclusion of the company here serves as a correction to that notice.
                    </P>
                    <P>
                        <SU>6</SU>
                         Commerce inadvertently omitted two company names, Daksh Fasteners and Nishant Steel Industries, and incorrectly reproduced one company name, Shree Luxmi Fasteners, in the initiation notice that published on June 2, 2026. 
                        <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews,</E>
                         91 FR 32928, 32931 (June 2, 2026). Commerce is correcting those errors in this notice.
                    </P>
                    <P>
                        <SU>7</SU>
                         We received requests for reviews of the listed companies for this POR, however, this order has been revoked due to litigation. 
                        <E T="03">See Mattresses from Indonesia: Notice of Court Decision Not in Harmony with the Final Determination of Antidumping Duty Investigation; Notice of Amended Final Determination; and Notice of Revocation of Antidumping Order.</E>
                         Should the order be reinstated as a result of pending litigation, we will initiate on these requests at that time.
                    </P>
                    <P>
                        <SU>8</SU>
                         In the notice of initiation of administrative review published on March 31, 2026 (91 FR 15951) and a correction notice of initiation of administrative review published on May 4, 2026 (91 FR 23941), we initiated a review with respect to LG Electronics Reynosa, S.A. de C.V. and LG Electronics, U.S.A., Inc. We have now determined that LG Electronics Mexicali S.A. de C.V. had entries attributable to LG Electronics Reynosa S.A. de C.V., and, therefore, are including LG Electronics Mexicali S.A. de C.V. in this review.
                    </P>
                    <P>
                        <SU>9</SU>
                         In English, the name HDM Spiral Kaynakli Celik Boru A.S. is HDM Spirally Welded Steel Pipe Inc.
                    </P>
                    <P>
                        <SU>10</SU>
                         In English, the name Toscelik Profil ve Sac End. A.S. is Toscelik Profile and Sheet Ind. Co.
                    </P>
                    <P>
                        <SU>11</SU>
                         In 
                        <E T="03">Initiation of Antidumping and Countervailing Duty Administrative Reviews,</E>
                         91 FR 23941, 23944 (May 4, 2026), Commerce listed Go-Pak Paper Products Vietnam Co. but it should have been spelled as Go-Pak Paper Products Vietnam Co., Ltd.
                    </P>
                    <P>
                        <SU>12</SU>
                         Commerce published an incorrect POR in the opportunity notice associated with this review and hereby corrects the POR to reflect the actual period for this administrative review. 
                        <E T="03">
                            See Antidumping or 
                            <PRTPAGE/>
                            Countervailing Duty Order, Finding, or Suspended Investigation; Opportunity To Request Administrative Review and Join Annual Inquiry Service List; Note Regarding Format of Review Requests,
                        </E>
                         91 FR 23956 (May 4, 2026).
                    </P>
                    <P>
                        <SU>13</SU>
                         In 
                        <E T="03">Initiation of Antidumping and Countervailing Duty Administrative Reviews,</E>
                         91 FR 32928, 32932 (June 2, 2026), Commerce listed Ningbo Dongxin High-Strength Nut, Zhejiang Junyue Standard Parts Co., Ltd., and Ningbo Zhenghai Yongding Fastener but they should have been spelled as Ningbo Dongxin High-Strength Nut Co., Ltd., Zhejiang Junyue Standard Part Co., Ltd., and Ningbo Zhenghai Yongding Fastener Co., Ltd., respectively.
                    </P>
                    <P>
                        <SU>14</SU>
                         Commerce inadvertently included a statement in footnote 5 of the initiation notice for the April anniversary month which was not applicable. All companies for which Commerce received a request for review of this order were identified in the initiation notice for the April anniversary month. 
                        <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews,</E>
                         91 FR 32928, 32932 (June 2, 2026).
                    </P>
                    <P>
                        <SU>15</SU>
                         In the initiation notice that published on March 31, 2026 (91 FR 15951), Commerce inadvertently omitted certain notes for certain companies under administrative review. Commerce hereby clarifies the full company names under administrative review.
                    </P>
                    <P>
                        <SU>16</SU>
                         Allied Pacific Food (Dalian) Co., Ltd., Allied Pacific (HK) Co., Ltd., Allied Pacific Aquatic Products (Zhanjiang) Co., Ltd; and Allied Pacific Aquatic Products (Zhongshan) Co., Ltd. comprise the single entity Allied Pacific.
                    </P>
                    <P>
                        <SU>17</SU>
                         Shantou Red Garden Food Processing Co., Ltd., and Shantou Red Garden Foodstuff Co., Ltd., comprise the single entity Shantou Red Garden Foods.
                    </P>
                    <P>
                        <SU>18</SU>
                         This Order was revoked with respect to subject merchandise produced and exported by Zhanjiang Guolian Aquatic Products Co., Ltd. 
                        <E T="03">See Notice of Amended Final Determination of Sales at Less Than Fair Value and Antidumping Duty Order: Certain Frozen Warmwater Shrimp from the People's Republic of China,</E>
                         70 FR 5149, 5152 (February 1, 2005). Accordingly, we initiated this review for this exporter only with respect to subject merchandise produced by another entity.
                    </P>
                    <P>
                        <SU>19</SU>
                         This Order was revoked with respect to subject merchandise produced and exported by Zhanjiang Regal Integrated Marine Resources Co., Ltd. 
                        <E T="03">See Certain Frozen Warmwater Shrimp from the People's Republic of China: Final Results of Administrative Review; 2011-2012,</E>
                         78 FR 56209, 56210 (September 12, 2013). Accordingly, we initiated this review for this exporter only with respect to subject merchandise produced by another entity.
                    </P>
                    <P>
                        <SU>20</SU>
                         Commerce previously determined that Companhia de Ferro Ligas da Bahia-FERBASA and Fundacao Jose Carvalho Foundation are cross-owned companies. 
                        <E T="03">See Ferrosilicon from Brazil: Final Affirmative Countervailing Duty Determination and Final Affirmative Critical Circumstances Determination, In Part,</E>
                         90 FR 14114 (March 28, 2025) (
                        <E T="03">Ferrosilicon from Brazil</E>
                        ). Absent information to the contrary, we intend to continue to treat these entities as cross-owned for the purpose of this administrative review.
                    </P>
                    <P>
                        <SU>21</SU>
                         Commerce previously determined that Minasligas S.A., Irmazi Participacoes S.A., Participacoes SZ Ltd., and Centrium Empreendimentos Ltda are cross-owned companies. 
                        <E T="03">See Ferrosilicon from Brazil.</E>
                         Absent information to the contrary, we intend to continue to treat these entities as cross-owned for the purpose of this administrative review.
                    </P>
                    <P>
                        <SU>22</SU>
                         Commerce previously determined that OM Materials (Sarawak) Sdn Bhd., OM Materials &amp; Logistics (M) Sdn. Bhd., OM Materials (Samalaju) Sdn. Bhd., and OM Engineering Tech (M) Sdn. Bhd. are cross-owned companies. 
                        <E T="03">See Ferrosilicon from Malaysia: Final Affirmative Countervailing Duty Determination and Final Affirmative Determination of Critical Circumstances, in Part,</E>
                         90 FR 14075 (March 28, 2025).
                    </P>
                    <P>
                        <SU>23</SU>
                         In past proceedings, Commerce has found these companies to be cross-owned. 
                        <E T="03">See Certain Carbon and Alloy Steel Cut-to- Length Plate From the Republic of Korea: Final Results of Countervailing Duty Administrative Review; 2023,</E>
                         91 FR 27264-65 (May 14, 2026); 
                        <E T="03">see also Certain Carbon and Alloy Steel Cut-to- Length Plate From the Republic of Korea: Final Results of Countervailing Duty Administrative Review; 2022,</E>
                         89 FR 99224-25 (December 10, 2024). Absent information to the contrary, we intend to continue to treat these entities as cross-owned for the purpose of this administrative review.
                    </P>
                    <P>
                        <SU>24</SU>
                         In their request for administrative review, Cleveland-Cliffs Inc., Nucor Corporation, and SSAB Enterprises LLC requested review of “POSCO International Corp.” which is an abbreviation of the full company name. We listed here only the full company name, as it appears in the company's request for review.
                    </P>
                    <P>
                        <SU>25</SU>
                         Subject merchandise both produced and exported by Husteel Co., Ltd. (Husteel) is excluded from the countervailing duty order. 
                        <E T="03">See Large Diameter Welded Pipe from the Republic of Korea: Countervailing Duty Order,</E>
                         84 FR 18773 (May 2, 2019). Thus, Husteel's inclusion in this administrative review is limited to entries for which Husteel was not both the producer and exporter of the subject merchandise.
                    </P>
                    <P>
                        <SU>26</SU>
                         Subject merchandise both produced and exported by Hyundai Steel Company (Hyundai Steel) and subject merchandise produced by Hyundai Steel and exported by Hyundai Corporation are excluded from the countervailing duty order. 
                        <E T="03">See Large Diameter Welded Pipe from the Republic of Korea: Countervailing Duty Order,</E>
                         84 FR 18773 (May 2, 2019). Thus, Hyundai Steel's inclusion in this administrative review is limited to entries for which Hyundai Steel was not both the producer and exporter of subject merchandise.
                    </P>
                    <P>
                        <SU>27</SU>
                         In English, the name HDM Spiral Kaynakli Celik Boru A.S. is HDM Spirally Welded Steel Pipe Inc.
                    </P>
                    <P>
                        <SU>28</SU>
                         In English, the name Toscelik Profil ve Sac End. A.S. is Toscelik Profile and Sheet Ind. Co.
                    </P>
                    <P>
                        <SU>29</SU>
                         Commerce previously determined that Qingdao CIMC Special Vehicles Co., Ltd., Dongguan CIMC Vehicle Co., Ltd., CIMC Vehicles (Group) Co., Ltd., Shenzhen CIMC Vehicle Co., Ltd., Zhumadian CIMC Huajun Casting Co., Ltd., China International Marine Containers (Group) Co., Ltd., Liangshan CIMC Dongyue Vehicles Co., Ltd., Shandong Wanshida Special Vehicle Manufacturing Co., Ltd., Yangzhou CIMC Tonghua Special Vehicles Co., Ltd., Zhumadian CIMC Huajun Vehicle Co., Ltd., Gansu CIMC Huajun Vehicles Co., Ltd., CIMC Vehicles (Liaoning) Co., Ltd., and Zhumadian CIMC Wanjia Axle Co., Ltd. are cross-owned companies. 
                        <E T="03">See Certain Chassis and Subassemblies Thereof from the People's Republic of China: Final Affirmative Countervailing Duty Determination,</E>
                         86 FR 15186 (March 22, 2021).
                    </P>
                    <P>
                        <SU>30</SU>
                         In the May 4, 2026 Initiation Notice for Certain Corrosion Inhibitors from the People's Republic of China (C-570-123), Commerce inadvertently did not list the companies previously determined to be cross-owned with Nantong Botao Chemical Co. Ltd. (
                        <E T="03">i.e.,</E>
                         Nantong Yutu Group Co., Ltd., Rugao Connect Chemical Co., Ltd., and Rugao Jinling Chemical Co., Ltd.). Further, we also did not list the companies previously determined to be cross-owned with Anhui Trust Chem Co., Ltd. (
                        <E T="03">i.e.,</E>
                         Nanjing Trust Chem Co., Ltd. and Jiangsu Trust Chem Co., Ltd.), and the former company name of Kanghua Chemical Co., Ltd. (
                        <E T="03">i.e.,</E>
                         Nantong Kanghua Chemical Co., Ltd.). 
                        <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews,</E>
                         91 FR 23941 (May 4, 2026); 
                        <E T="03">see also Certain Corrosion Inhibitors from the People's Republic of China: Final Results of Countervailing Duty Administrative Review; 2023,</E>
                         91 FR 12139 (March 12, 2026).
                    </P>
                    <P>
                        <SU>31</SU>
                         Commerce determined that Jiangxi Tianyu Chemical Co., Ltd., is cross-owned with Thai Harvest Ltd., CAC Nantong Chemical Co., Ltd., and CAC Shanghai International Trading Co., Ltd. 
                        <E T="03">See, e.g., 2,4-Dichlorophenoxyacetic Acid from the People's Republic of China: Final Affirmative Countervailing Duty Determination,</E>
                         90 FR 14957, 14958 n.6 (April 7, 2025).
                    </P>
                    <P>
                        <SU>32</SU>
                         In 
                        <E T="03">Initiation of Antidumping and Countervailing Duty Administrative Reviews,</E>
                         91 FR 32928, 32934 (June 2, 2026), Commerce listed Ningbo Dongxin High-Strength Nut, Ningbo Zhongjiang High Strength Bolts Co., Ltd., Zhejiang Junyue Standard Parts Co Ltd., and Ningbo Zhenghai Yongding Fastener. Ningbo Dongxin High-Strength Nut, Zhejiang Junyue Standard Parts Co Ltd., and Ningbo Zhenghai Yongding Fastener should have been spelled as Ningbo Dongxin High-Strength Nut Co., Ltd., Zhejiang Junyue Standard Part Co., Ltd., and Ningbo Zhenghai Yongding Fastener Co., Ltd., respectively. In the same initiation notice, for this review, we inadvertently omitted the cross-owned companies of certain respondents as follows Ningbo Zhongjiang High Strength Bolts Co., Ltd., and its cross-owned company Ningbo Zhongmin Metal Product Co., Ltd.; Zhejiang Junyue Standard Part Co., Ltd., and its cross-owned companies Jiaxing Chengyue Trading Co., Ltd., and Haiyan County Brother Paper Industry Co., Ltd.; and Ningbo Zhenghai Yongding Fastener Co., Ltd., and its cross-owned company Ningbo Yongzan Machinery Parts Co., Ltd. 
                        <E T="03">See Carbon and Alloy Steel Threaded Rod from the People's Republic of China: Final Results of Countervailing Duty Administrative Review; 2019-2020,</E>
                         87 FR 67016, 67017 n.1, n.2 (November 7, 2022), and 
                        <E T="03">Carbon and Alloy Steel Threaded Rod from the People's Republic of China: Final Results of Countervailing Duty Administrative Review; 2022,</E>
                         89 FR 57131 n.6 (July 12, 2024).
                    </P>
                </FTNT>
                <PRTPAGE P="42424"/>
                <HD SOURCE="HD1">Duty Absorption Reviews</HD>
                <P>During any administrative review covering all or part of a period falling between the first and second or third and fourth anniversary of the publication of an AD order under 19 CFR 351.211 or a determination under 19 CFR 351.218(f)(4) to continue an order or suspended investigation (after sunset review), Commerce, if requested by a domestic interested party within 30 days of the date of publication of the notice of initiation of the review, will determine whether antidumping duties have been absorbed by an exporter or producer subject to the review if the subject merchandise is sold in the United States through an importer that is affiliated with such exporter or producer. The request must include the name(s) of the exporter or producer for which the inquiry is requested.</P>
                <HD SOURCE="HD1">Gap Period Liquidation</HD>
                <P>
                    For the first administrative review of any order, there will be no assessment of antidumping or countervailing duties on entries of subject merchandise entered, or withdrawn from warehouse, for consumption during the relevant “gap” period of the order (
                    <E T="03">i.e.,</E>
                     the period following the expiry of provisional measures and before 
                    <PRTPAGE P="42425"/>
                    definitive measures were put into place), if such a gap period is applicable to the POR.
                </P>
                <HD SOURCE="HD1">Administrative Protective Orders and Letters of Appearance</HD>
                <P>
                    Interested parties must submit applications for disclosure under administrative protective orders in accordance with the procedures outlined in Commerce's regulations at 19 CFR 351.305. Those procedures apply to administrative reviews included in this notice of initiation. Parties wishing to participate in any of these administrative reviews should ensure that they meet the requirements of these procedures (
                    <E T="03">e.g.,</E>
                     the filing of separate letters of appearance as discussed at 19 CFR 351.103(d)).
                </P>
                <HD SOURCE="HD1">Factual Information Requirements</HD>
                <P>
                    Commerce's regulations identify five categories of factual information in 19 CFR 351.102(b)(21), which are summarized as follows: (i) evidence submitted in response to questionnaires; (ii) evidence submitted in support of allegations; (iii) publicly available information to value factors under 19 CFR 351.408(c) or to measure the adequacy of remuneration under 19 CFR 351.511(a)(2); (iv) evidence placed on the record by Commerce; and (v) evidence other than factual information described in (i)-(iv). These regulations require any party, when submitting factual information, to specify under which subsection of 19 CFR 351.102(b)(21) the information is being submitted and, if the information is submitted to rebut, clarify, or correct factual information already on the record, to provide an explanation identifying the information already on the record that the factual information seeks to rebut, clarify, or correct. The regulations, at 19 CFR 351.301, also provide specific time limits for such factual submissions based on the type of factual information being submitted. Please review the 
                    <E T="03">Final Rule,</E>
                    <SU>33</SU>
                    <FTREF/>
                     available at 
                    <E T="03">https://www.govinfo.gov/content/pkg/FR-2013-07-17/pdf/2013-17045.pdf,</E>
                     prior to submitting factual information in this segment. Note that Commerce has amended certain of its requirements pertaining to the service of documents in 19 CFR 351.303(f).
                    <SU>34</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">See Certification of Factual Information To Import Administration During Antidumping and Countervailing Duty Proceedings,</E>
                         78 FR 42678 (July 17, 2013) (
                        <E T="03">Final Rule</E>
                        ); 
                        <E T="03">see also</E>
                         the frequently asked questions regarding the 
                        <E T="03">Final Rule,</E>
                         available at 
                        <E T="03">https://enforcement.trade.gov/tlei/notices/factual_info_final_rule_FAQ_07172013.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         
                        <E T="03">See Administrative Protective Order, Service, and Other Procedures in Antidumping and Countervailing Duty Proceedings; Final Rule,</E>
                         88 FR 67069 (September 29, 2023).
                    </P>
                </FTNT>
                <P>
                    Any party submitting factual information in an AD or CVD proceeding must certify to the accuracy and completeness of that information using the formats provided at the end of the 
                    <E T="03">Final Rule.</E>
                    <SU>35</SU>
                    <FTREF/>
                     Commerce intends to reject factual submissions in any proceeding segments if the submitting party does not comply with applicable certification requirements.
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         
                        <E T="03">See</E>
                         section 782(b) of the Act; 
                        <E T="03">see also Final Rule;</E>
                         and the frequently asked questions regarding the 
                        <E T="03">Final Rule,</E>
                         available at 
                        <E T="03">https://enforcement.trade.gov/tlei/notices/factual_info_final_rule_FAQ_07172013.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Extension of Time Limits Regulation</HD>
                <P>
                    Parties may request an extension of time limits before a time limit established under Part 351 expires, or as otherwise specified by Commerce.
                    <SU>36</SU>
                    <FTREF/>
                     In general, an extension request will be considered untimely if it is filed after the time limit established under Part 351 expires. For submissions which are due from multiple parties simultaneously, an extension request will be considered untimely if it is filed after 10:00 a.m. on the due date. Examples include, but are not limited to: (1) case and rebuttal briefs, filed pursuant to 19 CFR 351.309; (2) factual information to value factors under 19 CFR 351.408(c), or to measure the adequacy of remuneration under 19 CFR 351.511(a)(2), filed pursuant to 19 CFR 351.301(c)(3) and rebuttal, clarification and correction filed pursuant to 19 CFR 351.301(c)(3)(iv); (3) comments concerning the selection of a surrogate country and surrogate values and rebuttal; (4) comments concerning CBP data; and (5) Q&amp;V questionnaires. Under certain circumstances, Commerce may elect to specify a different time limit by which extension requests will be considered untimely for submissions which are due from multiple parties simultaneously. In such a case, Commerce will inform parties in the letter or memorandum setting forth the deadline (including a specified time) by which extension requests must be filed to be considered timely. This policy also requires that an extension request must be made in a separate, standalone submission, and clarifies the circumstances under which Commerce will grant untimely-filed requests for the extension of time limits. Please review the 
                    <E T="03">Final Rule,</E>
                     available at 
                    <E T="03">https://www.gpo.gov/fdsys/pkg/FR-2013-09-20/html/2013-22853.htm,</E>
                     prior to submitting factual information in these segments.
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         
                        <E T="03">See</E>
                         19 CFR 351.302.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>These initiations and this notice are in accordance with section 751(a) of the Act (19 U.S.C. 1675(a)) and 19 CFR 351.221(c)(1)(i).</P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Christian L. Bush,</NAME>
                    <TITLE>Deputy Assistant Secretary for Policy and Negotiations.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13892 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMISSION OF FINE ARTS</AGENCY>
                <SUBJECT>Notice of Meeting</SUBJECT>
                <P>Per 45 CFR Chapter XXI § 2102.3, the next meeting of the U.S. Commission of Fine Arts is scheduled for July 16, 2026, at 9:00 a.m. and will be held in the Commission offices at the National Building Museum, Suite 312, Judiciary Square, 401 F Street NW, Washington, DC 20001-2728. Items of discussion may include buildings, infrastructure, parks, memorials, and public art.</P>
                <P>
                    Draft agendas and additional information regarding the Commission are available on our website: 
                    <E T="03">www.cfa.gov.</E>
                     Inquiries regarding the agenda, as well as any public testimony, and requests to submit written or oral statements should be addressed to Thomas Luebke, Secretary, U.S. Commission of Fine Arts, at the above address; by emailing 
                    <E T="03">cfastaff@cfa.gov;</E>
                     or by calling 202-504-2200. Individuals requiring sign language interpretation for the hearing impaired should contact the Secretary at least 10 days before the meeting date.
                </P>
                <SIG>
                    <DATED>Dated July 6, 2026 in Washington, DC.</DATED>
                    <NAME>Zakiya N. Walters,</NAME>
                    <TITLE>Administrative Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13812 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6330-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMITTEE FOR PURCHASE FROM PEOPLE WHO ARE BLIND OR SEVERELY DISABLED</AGENCY>
                <SUBJECT>Procurement List; Deletions</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Deletions from the Procurement List.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action deletes service(s) from the Procurement List that were furnished by nonprofit agencies employing persons who are blind or have other severe disabilities.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Date added to and deleted from the Procurement List:</E>
                         August 09, 2026.
                    </P>
                </DATES>
                <ADD>
                    <PRTPAGE P="42426"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled, 250 E Street SW, Suite 3100, Washington, DC 20024.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For further information or to submit comments contact: Michael R. Jurkowski, Telephone: (703) 489-1322, or email 
                        <E T="03">CMTEFedReg@AbilityOne.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Deletions</HD>
                <P>On June 4, 2026 (91 FR 33705), the Committee for Purchase From People Who Are Blind or Severely Disabled published notice of proposed deletions from the Procurement List. This notice is published pursuant to 41 U.S.C. 8503(a)(2) and 41 CFR 51-2.3.</P>
                <P>After consideration of the relevant matter presented, the Committee has determined that the service(s) listed below are no longer suitable for procurement by the Federal Government under 41 U.S.C. 8501-8506 and 41 CFR 51-2.4.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act Certification</HD>
                <P>I certify that the following action will not have a significant impact on a substantial number of small entities. The major factors considered for this certification were:</P>
                <P>1. The action will not result in additional reporting, recordkeeping or other compliance requirements for small entities.</P>
                <P>2. The action may result in authorizing small entities to furnish the service(s) to the Government.</P>
                <P>3. There are no known regulatory alternatives which would accomplish the objectives of the Javits-Wagner-O'Day Act (41 U.S.C. 8501-8506) in connection with the service(s) deleted from the Procurement List.</P>
                <HD SOURCE="HD1">End of Certification</HD>
                <P>Accordingly, the following service(s) are deleted from the Procurement List:</P>
                <EXTRACT>
                    <HD SOURCE="HD2">Service(s)</HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type:</E>
                         Custodial Service
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Mandatory For:</E>
                         Bureau of Land Management, Aguirre Spring Campground, Dripping Springs Natural Area and Organ Mountain Recreation Site, Organ, NM, 15000 Aguirre Springs Road, Organ, NM
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Tresco, Inc., Las Cruces, NM
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         DEPARTMENT OF THE INTERIOR, BLM ALBUQUERQUE DISTRICT OFFICE
                    </FP>
                    <HD SOURCE="HD2">Service(s)</HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type:</E>
                         Courier Service
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Mandatory For:</E>
                         Department of Homeland Security, Immigrations &amp; Customs Enforcement, Office of Chief Counsel, El Paso, TX, 11541 Montana Avenue, Suite O, El Paso, TX
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Training, Rehabilitation, &amp; Development Institute, Inc., San Antonio, TX
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         DEPARTMENT OF HOMELAND SECURITY, MISSION SUPPORT ORLANDO
                    </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Michael R. Jurkowski,</NAME>
                    <TITLE>Director, Business Operations.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13839 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6353-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">COMMITTEE FOR PURCHASE FROM PEOPLE WHO ARE BLIND OR SEVERELY DISABLED</AGENCY>
                <SUBJECT>Procurement List; Proposed Additions and Deletions</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed additions to and deletions from the Procurement List.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Committee is proposing to add products to the Procurement List that will be furnished by nonprofit agencies employing persons who are blind or have other severe disabilities, and delete product(s) and service(s) previously furnished by such agencies.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments must be received on or before:</E>
                         August 08, 2026.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled, 250 E Street SW, Suite 3100, Washington, DC 20024.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For further information or to submit comments contact: Michael R. Jurkowski, Telephone: (703) 489-1322, or email 
                        <E T="03">CMTEFedReg@AbilityOne.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice is published pursuant to 41 U.S.C. 8503 (a)(2) and 41 CFR 51-2.3. Its purpose is to provide interested persons an opportunity to submit comments on the proposed actions.</P>
                <HD SOURCE="HD1">Additions</HD>
                <P>
                    In accordance with 41 CFR 51-2.4(b), Government personnel within the contracting activity have identified the product listed below as a requirement not applicable to other Federal entities and has requested the Committee consider granting a purchase or distribution preference if the product is added to the Procurement List. 
                    <E T="03">See</E>
                     71 FR 69536 (Dec. 1, 2006). If the Committee grants this request, the product will not be available through the U.S. AbilityOne Commission's Commercial Distribution Program. The Committee will consider this request along with relevant comments received from interested parties.
                </P>
                <P>The following product(s) are proposed for addition to the Procurement List for production by the nonprofit agencies listed:</P>
                <EXTRACT>
                    <HD SOURCE="HD2">Product(s)</HD>
                    <FP SOURCE="FP-2">NSN(s)—Product Name(s):</FP>
                    <FP SOURCE="FP1-2">7930-01-660-1605—Navy Cleaning Kit</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Louisiana Association for the Blind, Shreveport, LA
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Mandatory For:</E>
                         DEPT OF DEFENSE
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         DEPT OF DEFENSE, DLA TROOP SUPPORT
                    </FP>
                </EXTRACT>
                <HD SOURCE="HD1">Deletions</HD>
                <P>The following product(s) and service(s) are proposed for deletion from the Procurement List:</P>
                <EXTRACT>
                    <HD SOURCE="HD2">Product(s)</HD>
                    <FP SOURCE="FP-2">NSN(s)—Product Name(s):</FP>
                    <FP SOURCE="FP1-2">5340-00-916-4206—Hanger, Magnetic, Picture, Gray, 3″ x 3″</FP>
                    <FP SOURCE="FP1-2">7240-01-318-5222—Tripod Cradle, Military Fuel Can</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Sunshine Services, Knoxville, TN
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         GENERAL SERVICES ADMINISTRATION, GSA/FSS GREATER SOUTHWEST ACQUISITI
                    </FP>
                    <FP SOURCE="FP-2">NSN(s)—Product Name(s): 3910-01-000-3015—Tow Pin, Steel Mail Cart, 26.5″</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Rauch, Inc., New Albany, IN
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         US Postal Service, USPS, Topeka Purchasing Center
                    </FP>
                    <FP SOURCE="FP-2">NSN(s)—Product Name(s):</FP>
                    <FP SOURCE="FP1-2">7520-01-620-3315—Hole Punch, Paper, High-capacity, 3-Hole, Adjustable, 32 sheet capacity, Black Base, Metallic Handle </FP>
                    <FP SOURCE="FP1-2">7520-01-620-3827—Hole Punch, Paper, Light Duty, 3-Hole, Adjustable, 10 sheet capacity, Black</FP>
                    <FP SOURCE="FP1-2">7520-01-620-3828—Hole Punch, Paper, Light Duty, 3-Hole, Adjustable, 8 sheet capacity, Black </FP>
                    <FP SOURCE="FP1-2">7520-01-620-3829—Hole Punch, Paper, Light Duty, 3-Hole, Adjustable, 10 sheet capacity, Metallic Base, Black Handle </FP>
                    <FP SOURCE="FP1-2">7520-01-620-8390—Hole Punch, Paper, Desktop, 3-Hole, Adjustable, 15 sheet capacity, Metallic Base, Black Grip</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Access: Supports for Living Inc., Middletown, NY
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         GENERAL SERVICES ADMINISTRATION, GSA/FAS ADMIN SVCS ACQUISITION BR(2
                    </FP>
                    <FP SOURCE="FP-2">
                        NSN(s)—Product Name(s): 8445-00-549-5363—Scarf, Woman's, U.S. Navy, White, 47″ x 10
                        <FR>3/4</FR>
                        ″
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         LIONS INDUSTRIES FOR THE BLIND, INC, Kinston, NC
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         DEPT OF DEFENSE, DLA TROOP SUPPORT
                    </FP>
                    <FP SOURCE="FP-2">NSN(s)—Product Name(s): 8465-01-465-2080—Woodland &amp; Desert Pattern 8465-01-524-7639—Universal Pattern</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Winston-Salem Industries for the Blind, Inc, Winston-Salem, NC, Winston-Salem Industries for the Blind, Inc, Winston-Salem, NC
                        <PRTPAGE P="42427"/>
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         DEPT OF DEFENSE, W6QK ACC-APG NATICK,DEPT OF DEFENSE, DLA TROOP SUPPORT
                    </FP>
                    <FP SOURCE="FP-2">NSN(s)—Product Name(s):</FP>
                    <FP SOURCE="FP1-2">6505-01-575-8540—Rehydration Salts, Oral, Orange, 12.5g </FP>
                    <FP SOURCE="FP1-2">6505-01-575-8578—Rehydration Salts, Oral, Pomegranate Acai Blueberry, 12.5g</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Alphapointe, Kansas City, MO
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         DEPT OF DEFENSE, DLA TROOP SUPPORT
                    </FP>
                    <FP SOURCE="FP-2">NSN(s)—Product Name(s):</FP>
                    <FP SOURCE="FP1-2">7930-01-436-8067—Cleaner, Extraction, Concentrate, 2 Liter</FP>
                    <FP SOURCE="FP1-2">7910-01-513-2238—Pad, Floor Polishing Machine, Topline Speed Burnishing, 3200 Series, Peach, 14″</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Beacon Lighthouse, Inc., Wichita Falls, TX
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         VETERANS AFFAIRS, DEPARTMENT OF, STRATEGIC ACQUISITION CENTER
                    </FP>
                    <HD SOURCE="HD2">Service(s)</HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type:</E>
                         Alarm Monitor and Reception Services
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Mandatory For:</E>
                         US Army, Defense Forensic Science Center and Forensic Exploitation Directorate, Fort Gillem, Forest Park, GA, 4930 N 31st Street, Gillem Enclave, Forest Park, GA
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Bobby Dodd Institute, Inc., Atlanta, GA
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         DEPT OF DEFENSE, W6QM MICC-FT EISENHOWER
                    </FP>
                    <HD SOURCE="HD2">Service(s)</HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type:</E>
                         Third Party Logistics Service
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Mandatory For:</E>
                         Product Manager Force Sustainment Services, Natick, MA, 15 Kansas Street, Natick, MA
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         ReadyOne Industries, Inc., El Paso, TX
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         DEPT OF DEFENSE, W6QK ACC-APG NATICK
                    </FP>
                    <HD SOURCE="HD2">Service(s)</HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type:</E>
                         Relooping of Link Tube Carrier
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Mandatory For:</E>
                         U.S. Army, Army Contracting Command Rock Island, Rock Island, IL, Buildings 60 &amp; 62, Rock Island, IL
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Rolling Hills Progress Center, Inc., Lanark, IL
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         DEPT OF DEFENSE, W4MM USA JOINT MUNITIONS CMD
                    </FP>
                    <HD SOURCE="HD2">Service(s)</HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type:</E>
                         Transcription Service
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Mandatory For:</E>
                         U.S. Navy, Naval Medical Logistics Command, Fort Detrick, MD, 693 Neiman Street, Fort Detrick, MD
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Authorized Source of Supply:</E>
                         Lighthouse for the Blind of Houston, Houston, TX
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contracting Activity:</E>
                         DEPT OF DEFENSE, DEFENSE HEALTH AGENCY (DHA)
                    </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Michael R. Jurkowski,</NAME>
                    <TITLE>Director, Business Operations.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13840 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6353-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE</AGENCY>
                <SUBAGY>Department of the Air Force</SUBAGY>
                <SUBJECT>Notice of Federal Advisory Committee Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Visitors of the U.S. Air Force Academy (BoV AFA), Department of the Air Force.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of partially closed Federal advisory committee meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P> The Department of Defense is publishing this notice to announce that the following Federal advisory committee meeting of the Board of Visitors of the U.S. Air Force Academy (BoV AFA) will take place.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Open to the public Monday, July 20, 2026 from approximately 1:20 p.m. to 3:15 p.m. Eastern Time Zone (ET). Closed to the public from approximately 1:00 p.m. to 1:20 p.m. ET</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The meeting will occur virtually. The link for the virtual meeting accessible to the public can be found at: 
                        <E T="03">https://www.usafa.edu/about/bov/</E>
                         and will be active approximately thirty minutes before the start of the meeting.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <P>
                        <E T="03">Designated Federal Officer:</E>
                         Dr. Raquel Rimpola, 
                        <E T="03">USAFA.HQ.BOV@us.af.mil,</E>
                         703-693-2767, 1660 Air Force Pentagon, Washington DC, 20330-1660.
                    </P>
                    <P>
                        <E T="03">Alternate Designated Federal Officer:</E>
                         Ms. Blaire Brush, 
                        <E T="03">USAFA.HQ.BOV@us.af.mil,</E>
                         2304 Cadet Drive, Suite 3200, USAF Academy, CO 80840-5025.
                    </P>
                    <P>
                        <E T="03">USAFA BoV Website: https://www.usafa.edu/about/bov/.</E>
                         Contains information on the Board of Visitors, link to the virtual meeting, and approved meeting agenda.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This meeting is being held under the provisions of the Federal Advisory Committee Act (FACA) (5 U.S.C. 1001 
                    <E T="03">et seq.</E>
                    ), the Government in the Sunshine Act (5 U.S.C. 552b), and 41 CFR 102-3.140 and 102-3.150.
                </P>
                <P>Pursuant to 41 CFR 102-3.140d, the committee is not obligated to allow a member of the public to speak or otherwise address the committee during the meeting and members of the public attending the committee meeting will not be permitted to present questions from the floor or speak to any issue under consideration of the committee.</P>
                <P>
                    <E T="03">Purpose of the Meeting:</E>
                     In accordance with 10 U.S.C. 9455(e)(1), the BoV AFA provides independent advice and recommendations to the Secretary of War, through the Secretary of the Air Force, on matters relating to the U.S. Air Force Academy (USAFA), including morale, discipline, and social climate, the curriculum, instruction, physical equipment, fiscal affairs, academic methods, and other matters relating to the USAFA that the BoV AFA decides to consider. This is a 2026 Organizational Meeting of the BoV AFA.
                </P>
                <P>The closed meeting from 1:00 p.m. to 1:20 p.m. ET on July 20, 2026, will consist of discussions of personnel actions that are pre-decisional in nature of which premature disclosure may significantly impact the implementation of a proposed action. For this reason, a portion of this meeting will be closed to the public, as the discussion of such information cannot be adequately segregated from other topics, which precludes opening the closed meeting to the public. The Principal Deputy Assistant Secretary of the Air Force for Manpower and Reserve Affairs, in consultation with the Office of General Counsel, has determined in writing that the meeting shall be partially closed to the public because the discussions during the closed meeting will be concerned with matters protected under section 552b(c)(9) of title 5, U.S.C.</P>
                <P>
                    <E T="03">Authority:</E>
                     5 U.S.C. 552b.
                </P>
                <P>
                    <E T="03">Written Statements:</E>
                     Pursuant to 41 CFR 102-3.105(j) and section 102-3.140 and section 1009(a)(3) of FACA, any member of the public wishing to provide input to the BoV AFA may submit a written statement. The public or interested organizations may submit written comments or statements to the Board about its mission and/or the topics to be addressed in the open sessions of this public meeting. Written comments or statements should be submitted to the Alternate Designated Federal Officer via electronic mail, at the email address listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section in the following formats: Adobe Acrobat and/or Microsoft Word. The comment or statement must include the author's name, title, affiliation, address, and daytime telephone number. Written comments or statements being submitted in response to the agenda set forth in this notice must be received at least five (5) business days prior to the meeting so they may be made available to the BoV Chairman for consideration prior to the meeting. Written comments or statements received after July 13, 2026, may not be provided to the BoV until its next meeting. Please note that because the BoV operates under FACA, all written comments will be treated as public documents and will be made available for public inspection.
                </P>
                <P>
                    <E T="03">Disability and Language Accommodations:</E>
                     Please direct any requests for disability or language accommodations to the Alternate 
                    <PRTPAGE P="42428"/>
                    Designated Federal Officer in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section above.
                </P>
                <SIG>
                    <NAME>Tommy W. Lee,</NAME>
                    <TITLE>Acting Air Force Federal Register Liaison Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13895 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3911-44-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
                <SUBJECT>President's Board of Advisors on Historically Black Colleges and Universities (HBCUs); Notice of Charter Renewal</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Department of Education.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of charter renewal.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given, in accordance with the Federal Advisory Committee Act of October 6, 1972, that the President's Board of Advisors on Historically Black Colleges and Universities (PBAHBCU), Department of Education, has been renewed for a 2-year period through April 9, 2028.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Sedika Franklin, Associate Director, President's Board of Advisors on Historically Black Colleges and Universities, U.S. Department of Education, 400 Maryland Ave. SW, Washington, DC 20024. Email: 
                        <E T="03">sedika.franklin@ed.gov.</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In accordance with the Federal Advisory Committee Act, as amended, the U.S. Department of Education is providing notice of the renewal of the charter of the President's Board of Advisors on Historically Black Colleges and Universities, Department of Education. This charter has been renewed for a two-year period through April 9, 2028.</P>
                <HD SOURCE="HD1">Public Interest Determination</HD>
                <P>Pursuant to 41 CFR 102-3.60(a), to establish, renew, reestablish, or merge a discretionary (agency discretion) advisory committee, an agency must first consult with the General Services Administration's Committee Management Secretariat (the Secretariat) and, as part of the consultation, provide a written public interest determination approved by the head of the agency to the Secretariat with a copy to the Office of Management and Budget. In addition, pursuant to 41 CFR 102-3.35, an agency shall follow the same consultation process and document in writing the same determination of need before creating a subcommittee under a discretionary committee that is not made up entirely of members of a parent advisory committee.</P>
                <P>Information on the following factors for the committee is provided to the Secretariat to demonstrate that renewing the committee is in the public interest:</P>
                <P>1. Annual budget: The U.S. Department of Education's estimated annual costs for operating the PBAHBCU, including Federal personnel and other Federal internal costs are as follows: a. Federal personnel on a full-time equivalent basis, $18,500; b. Other Federal internal costs, $2,000 for audio/visual and transcription services; and c. Projected costs for Board travel and accommodations, $40,000.</P>
                <P>2. If applicable, the total dollar value of grants expected to be recommended during the fiscal year, $0.</P>
                <P>3. Criteria for selecting members to ensure the committee has the necessary expertise and fairly balanced membership: The Board shall consist of not more than 21 members appointed by the President. The Secretary of Education and the Executive Director of the White House HBCU Initiative or their designees shall serve as ex officio members. In addition, the Board shall include sitting HBCU presidents as well as leaders from a variety of sectors, including education, philanthropy, business, finance, entrepreneurship, innovation, science and technology, and private foundations.</P>
                <P>4. List of all other Federal advisory committees of the agency:</P>
                <P>• Historically Black Colleges and Universities Capital Financing Advisory Board</P>
                <P>• National Advisory Committee on Institutional Quality and Integrity</P>
                <P>• National Advisory Council on Indian Education</P>
                <P>• National Board for Education Sciences</P>
                <P>• National Board of the Fund for the Improvement of Postsecondary Education (Inactive)</P>
                <P>• Safe and Drug-Free Schools and Communities Advisory Committee (Inactive)</P>
                <P>5. Justification that the information or advice provided by the Federal advisory committee or subcommittee is not available from another Federal advisory committee, another Federal Government source, or any other more cost-effective and less burdensome source: The Board shall advise the President, through the [White House HBCU] Initiative, on all matters pertaining to strengthening the educational capacity of HBCUs, which shall include the following:</P>
                <P>(i) improving the identity, visibility, distinctive capabilities, and overall competitiveness of HBCUs;</P>
                <P>(ii) engaging the philanthropic, business, government, military, homeland security, and education communities in a national dialogue regarding new HBCU programs and initiatives;</P>
                <P>(iii) improving the ability of HBCUs to remain fiscally secure institutions that can assist the Nation in achieving its educational goals and in advancing the interests of all Americans;</P>
                <P>(iv) elevating the public awareness of, and fostering appreciation of, HBCUs;</P>
                <P>(v) encouraging public-private investments in HBCUs; and</P>
                <P>(vi) improving government-wide strategic planning related to HBCU competitiveness to align Federal resources and provide the context for decisions about HBCU partnerships, investments, performance goals, priorities, human capital development and budget planning.</P>
                <P>6. If the consultation is a committee renewal, a summary of the previous accomplishments of the committee and the reasons it needs to continue:</P>
                <P>Summary of the previous accomplishments: The PBAHBCU has provided valuable insights to Presidents over many decades and has served as the primary convening body for HBCUs across the country.</P>
                <P>Reasons for the continuation: The PBAHBCU is a longstanding advisory committee that provides expert advice and insight on important African American institutions of higher education that have historically had a unique relationship with the Federal government. The continuance of this advisory board is essential for the President to receive valuable expertise on these institutions as American higher education transitions into artificial intelligence instruction and online learning.</P>
                <P>7. Explanation of why the committee/subcommittee is essential to the conduct of agency business:</P>
                <P>
                    The PBAHBCU issues an Annual Federal Plan for Assistance to Historically Black Colleges and Universities. This Plan is shared with the President and provides an overview on participation by HBCUs in federally sponsored programs. The Board also provides advice to the Secretary of Education and makes recommendations in reports to the President on how to increase the private sector role in strengthening HBCUs, with particular emphasis on enhancing institutional infrastructure and facilitating planning, development, and the use of new technologies to ensure the goal of long-term viability and enhancement of these institutions. This is valuable information about a unique group of historically and culturally important education institutions that is critical for the U.S. Department of Education to 
                    <PRTPAGE P="42429"/>
                    capitalize on in supporting American education.
                </P>
                <P>In conclusion, this public interest determination documents that renewing the committee is in the public interest, essential to the conduct of agency business, and that the information to be obtained is not already available through another advisory committee or source within the Federal Government.</P>
                <P>
                    The Assistant Secretary, Office of Postsecondary Education, U.S. Department of Education, has been delegated the authority to sign 
                    <E T="04">Federal Register</E>
                     notices pertaining to announcements of meetings and other committee management activities related to higher education.
                </P>
                <SIG>
                    <NAME>David Barker,</NAME>
                    <TITLE>Assistant Secretary, Office of Postsecondary Education, U.S. Department of Education.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13831 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBJECT>Notice of Availability of Draft 2026 National Transmission Needs Study and Request for Comment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Electricity, Department of Energy.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The U.S. Department of Energy (DOE) gives notice of availability of the draft 
                        <E T="03">2026 National Transmission Needs Study</E>
                         for public review and comment.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        DOE is currently accepting public comment from July 9, 2026 through September 8, 2026. Comments must be sent to 
                        <E T="03">NeedsStudy.Comments@hq.doe.gov</E>
                         by midnight EST, September 8, 2026.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested parties are to submit comments electronically to 
                        <E T="03">NeedsStudy.Comments@hq.doe.gov.</E>
                         DOE's guidance is available at: 
                        <E T="03">www.energy.gov/oe/national-transmission-needs-study.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Alissa Baker, U.S. Department of Energy, Office of Electricity, via (240) 702-4890; or 
                        <E T="03">NeedsStudy.Comments@hq.doe.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    DOE's Office of Electricity (OE) is announcing the availability of the draft 
                    <E T="03">2026 National Transmission Needs Study</E>
                     (2026 Needs Study) and requests public comment on the draft.
                </P>
                <P>Section 216(a) of the Federal Power Act (FPA), as amended by section 40105 of the Infrastructure Investment and Jobs Act (IIJA), requires DOE to conduct a study of electric transmission capacity constraints and congestion every three years. The 2026 Needs Study implements that statutory provision and OE published the last study in October 2023.</P>
                <P>Pursuant to section 216(a)(1), DOE is consulting with states, Tribes, and appropriate regional reliability entities regarding the 2026 Needs Study, including by providing a consultation draft for review and comment by these entities, as well as through additional outreach.</P>
                <P>
                    Pursuant to section 216(a)(2) of the FPA, the study would inform any decision to exercise DOE's National Interest Electric Transmission Corridor designation authority. The 2026 Needs Study will also inform DOE as it coordinates the use of other authorities and funding related to electric transmission. Members of the public can visit OE's website to access the public draft of the study as well as guidance for how to send comments or request further information at: 
                    <E T="03">www.energy.gov/oe/national-transmission-needs-study.</E>
                </P>
                <HD SOURCE="HD1">Signing Authority</HD>
                <P>
                    This document of the Department of Energy was signed on June 30, 2026, by Gilbert C. Bindewald III, Principal Deputy Assistant Secretary for the Office of Electricity, U.S. Department of Energy, pursuant to delegated authority from the Secretary of Energy. That document with the original signature and date is maintained by DOE. For administrative purposes only, and in compliance with requirements of the Office of the Federal Register, the undersigned DOE Federal Register Liaison Officer has been authorized to sign and submit the document in electronic format for publication, as an official document of the Department of Energy. The administrative process in no way alters the legal effect of this document upon publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <DATED>Signed in Washington, DC, on July 7, 2026.</DATED>
                    <NAME>Treena V. Garrett,</NAME>
                    <TITLE>Federal Register Liaison Officer, U.S. Department of Energy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13844 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBJECT>Renewal of the Electricity Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Electricity (OE), Department of Energy (DOE).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of renewal.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the Federal Advisory Committee Act and following consultation with the Committee Management Secretariat of the General Services Administration, notice is hereby given that the Electricity Advisory Committee (EAC) will be renewed for a two-year period. The Committee will provide advice, information, and recommendations to the Secretary of Energy on a continuing basis regarding policies and programs to modernize the nation's electric system.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The Board will be renewed on August 5, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Corinne Price, Designated Federal Officer, at 202-586-4037; email: 
                        <E T="03">corinne.price@hq.doe.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Committee members are chosen to assure well-balanced representation in terms of substantive technical expertise, institutional affiliation (
                    <E T="03">i.e.,</E>
                     State, industry, and university), geographic location, and any other considerations required. The EAC has members who represent interests outside of private industry, including academic, economic, labor, research, and state and tribal government interests. OE will continue to broadly reach out to interested individuals to find membership for the board through direct contact or expressions of interest via a 
                    <E T="04">Federal Register</E>
                     Notice. Membership and representation of all interests will be determined in accordance with the Federal Advisory Committee Act and its implementing regulations.
                </P>
                <P>The renewal of the Committee has been deemed essential to the Department of Energy's (DOE's) business and in public interest in conjunction with the performance of duties imposed upon the DOE, by law and agreement.</P>
                <P>
                    <E T="03">Public Interest Determination:</E>
                     Pursuant to 41 CFR 102-3.65(a), DOE is providing a written public interest determination, approved by the Secretary of Energy, detailing why this committee is essential to the conduct of agency business and that the information to be obtained is not already available through another advisory committee or source within the Federal Government.
                </P>
                <P>
                    <E T="03">1. Annual budget:</E>
                     Approximately $465,000 is planned for FY 27.
                </P>
                <P>
                    a. Federal personnel on a full-time equivalent (FTE) basis—The estimated annual person year of staff support required is one-half equivalent Federal full-time employee, at an estimated annual cost of $135,000.
                    <PRTPAGE P="42430"/>
                </P>
                <P>b. Other Federal internal costs—The estimate for other Federal internal costs, which include Federal travel, meeting/administrative expenses, and contractor costs, is $155,000.</P>
                <P>c. Proposed payments to members—The estimated payments for 60 non-Federal members are $0; the estimated salary of zero Federal members is $0.</P>
                <P>d. Proposed number of members—Approximately 60 members.</P>
                <P>e. Reimbursable costs—The estimate for reimbursable costs, including members' travel expenses, is approximately $175,000.</P>
                <P>
                    <E T="03">2. Total dollar value of grants expected to be recommended during the Fiscal Year:</E>
                     $0.
                </P>
                <P>
                    <E T="03">3. Criteria for selecting members to ensure the committee has the necessary expertise and fairly balanced membership:</E>
                     Committee members are chosen to assure well-balanced representation in terms of substantive technical expertise, institutional affiliation (
                    <E T="03">i.e.,</E>
                     State, industry, and university), geographic location, and any other considerations required. The EAC has members who represent interests outside of private industry, including academic, economic, labor, research, and state and tribal government interests. OE will continue to broadly reach out to interested individuals to find membership for the board through direct contact or expressions of interest via a 
                    <E T="04">Federal Register</E>
                     Notice. Membership and representation of all interests will be determined in accordance with the Federal Advisory Committee Act and its implementing regulations.
                </P>
                <P>
                    <E T="03">4. Other DOE Federal advisory committees:</E>
                </P>
                <FP SOURCE="FP-1">21st Century Energy Workforce Advisory Board</FP>
                <FP SOURCE="FP-1">Advisory Committee for Nuclear Security</FP>
                <FP SOURCE="FP-1">Biomass Research and Development Technical Advisory Committee</FP>
                <FP SOURCE="FP-1">Carbon Dioxide Capture, Utilization, and Sequestration Federal Lands Permitting Task Force</FP>
                <FP SOURCE="FP-1">Carbon Dioxide Capture, Utilization, and Sequestration Non-Federal Lands Permitting Task Force</FP>
                <FP SOURCE="FP-1">Electric Vehicle Working Group</FP>
                <FP SOURCE="FP-1">Environmental Management Site-Specific Advisory Board</FP>
                <FP SOURCE="FP-1">Hydrogen and Fuel Cell Technical Advisory Committee</FP>
                <FP SOURCE="FP-1">Isotope Research &amp; Development and Production Advisory Committee</FP>
                <FP SOURCE="FP-1">Industrial Technology Innovation Advisory Committee</FP>
                <FP SOURCE="FP-1">Methane Hydrate Advisory Committee</FP>
                <FP SOURCE="FP-1">National Coal Council</FP>
                <FP SOURCE="FP-1">National Petroleum Council</FP>
                <FP SOURCE="FP-1">National Quantum Initiative Advisory Committee</FP>
                <FP SOURCE="FP-1">President's Council of Advisors on Science and Technology</FP>
                <FP SOURCE="FP-1">Office of Science Advisory Committee</FP>
                <FP SOURCE="FP-1">Secretary of Energy Advisory Board</FP>
                <FP SOURCE="FP-1">State Energy Advisory Board</FP>
                <FP SOURCE="FP-1">Technical Panel on Magnetic Fusion</FP>
                <P>
                    <E T="03">5. Justification that the information or advice provided by the Federal advisory committee is not available from another Federal advisory committee, another Federal Government source, or any other more cost-effective and less burdensome source:</E>
                     No other advisory committee focuses only on the modernization of the nation's electric system. This board is uniquely suited to finding solutions to problems that the government alone cannot answer, and its advice cannot be obtained more economically through any means, such as public hearings.
                </P>
                <P>
                    <E T="03">6. Summary of the previous accomplishments of the committee and the reasons it needs to continue:</E>
                     Since the last charter renewal in August 2024, the EAC has met 2 times and produced several reports and recommendations that have benefited the Office of Electricity's policies and programs. The 3 EAC approved work products approved at the June 2025 meeting were the “
                    <E T="03">2024 Biennial Energy Storage Review</E>
                    ”, “
                    <E T="03">Bridging the Visibility Gap: Advancing Grid Resiliency and National Security With Last-Mile Digitization and Enhanced Distribution-Level Tools</E>
                    ”, and “
                    <E T="03">Resilient Communication for Grid Security: Enabling Private Broadband Networks for Critical Infrastructure,</E>
                    ” which provided recommendations across energy storage and grid resilience. Additionally, 4 recommendation reports are currently in development within the Grid Resilience for National Security, Smart Grid, and Energy Storage subcommittees. Further, the in-person full EAC meetings also included panels featuring noted thought leaders from the industry, regulatory bodies, public interest organizations, academic institutions and other stakeholders to provide DOE with invaluable feedback on Department initiatives and activities.
                </P>
                <P>
                    <E T="03">7. Explanation of why the committee is essential to the conduct of agency business:</E>
                     The EAC will help identify areas for the Office of Electricity to focus on and provide recommendations to aid in driving down electricity costs, securing our grid, increasing domestic energy production, and advancing critical technologies, such as artificial intelligence. Receiving outside input from industry, academia, and public interest groups is essential in developing sound policies on modernizing the U.S. electric system. The Committee will provide advice on many topics within the following broad subject areas:
                </P>
                <P>a. Advise DOE on current and future electric grid reliability, security, and policy issues of concern;</P>
                <P>b. Periodically review and make recommendations on DOE electric grid-related programs and initiatives, including electricity-related R&amp;D programs and deployment activities including technology development, technical assistance, modeling and analysis, and planning and policy;</P>
                <P>c. Identify emerging issues related to affordability, production, delivery, end-use, supply chain, reliability, security, modeling, and regulatory structures, and make recommendations, if appropriate, concerning DOE policy and initiatives;</P>
                <P>d. Make recommendations on how DOE can address the growing interdependence of and risk to critical electric infrastructure and other critical sectors such as defense, communications, and transportation;</P>
                <P>e. Advise on coordination between DOE, state, tribal, territorial, and regional officials and the private sector on matters affecting affordability, production, delivery, end-use, reliability, security, and economic and regulatory structures;</P>
                <P>f. Advise on coordination between Federal, State, tribal, territorial, and regional officials and the private sector in the event of supply disruption or other emergencies related to electric transmission, generation, and distribution; and</P>
                <P>g. Make recommendations to the Department on how to best implement programs or policies directly affecting all components of the electric system and its operations, as appropriate.</P>
                <HD SOURCE="HD1">Signing Authority</HD>
                <P>
                    This document was signed on July 7, 2026, by David Borak, Committee Management Officer, pursuant to delegated authority from the Secretary of Energy. That document with the original signature and date is maintained by the DOE. For administrative purposes only, and in compliance with requirements of the Office of the Federal Register, the undersigned DOE Federal Register Liaison Officer has been authorized to sign and submit the document in electronic format for publication, as an official document of the DOE. This administrative process in no way alters the legal effect of this document upon publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <PRTPAGE P="42431"/>
                    <DATED>Signed in Washington, DC, on July 7, 2026.</DATED>
                    <NAME>Jennifer Hartzell,</NAME>
                    <TITLE>Alternate Federal Register Liaison Officer, U.S. Department of Energy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13890 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. PF26-9-000]</DEPDOC>
                <SUBJECT>Transwestern Pipeline Company, LLC; Notice of Scoping Period Requesting Comments on Environmental Issues for the Planned Desert Southwest Expansion Project, and Notice of Public Scoping Sessions</SUBJECT>
                <P>The staff of the Federal Energy Regulatory Commission (FERC or Commission) will prepare an environmental document that will discuss the environmental effects of the Desert Southwest Expansion Project (Project) involving construction and operation of facilities by Transwestern Pipeline Company, LLC (Transwestern) in Texas, New Mexico, and Arizona. The Commission will use this environmental document in its decision-making process to determine whether the project is in the public convenience and necessity.</P>
                <P>
                    This notice announces the opening of the scoping process the Commission will use to gather input from the public and interested agencies regarding the Project. As part of the National Environmental Policy Act (NEPA) review process, the Commission takes into account concerns the public may have about proposals and the environmental effects that could result from its action whenever it considers the issuance of a Certificate of Public Convenience and Necessity. This gathering of public input is referred to as “scoping.” The main goal of the scoping process is to focus the analysis in the environmental document on the important environmental issues. Additional information about the Commission's NEPA process is described below in the 
                    <E T="03">NEPA Process and Environmental Document</E>
                     section of this notice.
                </P>
                <P>
                    By this notice, the Commission requests public comments on the scope of issues to address in the environmental document. To ensure that your comments are timely and properly recorded, please submit your comments so that the Commission receives them in Washington, DC on or before 5:00 p.m. Eastern Time on August 5, 2026. Comments may be submitted in written or oral form. Further details on how to submit comments are provided in the 
                    <E T="03">Public Participation</E>
                     section of this notice.
                </P>
                <P>Your comments should focus on the potential environmental effects, reasonable alternatives, and measures to avoid or lessen environmental effects. Your input will help the Commission staff determine what issues they need to evaluate in the environmental document. Commission staff will consider all written and oral comments during the preparation of the environmental document.</P>
                <P>If you submitted comments on this project to the Commission before the opening of this docket on March 27, 2026, you will need to file those comments in Docket No. PF26-9-000 to ensure they are considered.</P>
                <P>This notice is being sent to the Commission's current environmental mailing list for this project. State and local government representatives should notify their constituents of this planned project and encourage them to comment on their areas of concern.</P>
                <P>If you are a landowner receiving this notice, a pipeline company representative may contact you about the acquisition of an easement to construct, operate, and maintain the planned facilities. The company would seek to negotiate a mutually acceptable easement agreement. You are not required to enter into an agreement. However, if the Commission approves the project, the Natural Gas Act conveys the right of eminent domain to the company. Therefore, if you and the company do not reach an easement agreement, the pipeline company could initiate condemnation proceedings in court. In such instances, compensation would be determined by a judge in accordance with state law. The Commission does not subsequently grant, exercise, or oversee the exercise of that eminent domain authority. The courts have exclusive authority to handle eminent domain cases; the Commission has no jurisdiction over these matters.</P>
                <P>
                    A fact sheet prepared by the FERC entitled “An Interstate Natural Gas Facility On My Land? What Do I Need To Know?” addresses typically asked questions, including the use of eminent domain and how to participate in the Commission's proceedings. This fact sheet along with other landowner topics of interest are available for viewing on the FERC website (
                    <E T="03">www.ferc.gov</E>
                    ) under the Natural Gas, Landowner Topics link.
                </P>
                <HD SOURCE="HD1">Public Participation</HD>
                <P>
                    There are five methods you can use to submit your comments to the Commission. Please carefully follow these instructions so that your comments are properly recorded. The Commission encourages electronic filing of comments and has staff available to assist you at (866) 208-3676 or 
                    <E T="03">FercOnlineSupport@ferc.gov.</E>
                </P>
                <P>
                    (1) You can file your comments electronically using the eComment feature, which is located on the Commission's website (
                    <E T="03">www.ferc.gov</E>
                    ) under the link to FERC Online. Using eComment is an easy method for submitting brief, text-only comments on a project;
                </P>
                <P>
                    (2) You can file your comments electronically by using the eFiling feature, which is located on the Commission's website (
                    <E T="03">www.ferc.gov</E>
                    ) under the link to FERC Online. With eFiling, you can provide comments in a variety of formats by attaching them as a file with your submission. New eFiling users must first create an account by clicking on “eRegister.” You will be asked to select the type of filing you are making; a comment on a particular project is considered a “Comment on a Filing”; or
                </P>
                <P>(3) You can file a paper copy of your comments by mailing them to the Commission. Be sure to reference the project docket number (PF26-9-000) on your letter. Submissions sent via the U.S. Postal Service must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Room 1A, Washington, DC 20426. Submissions sent via any other carrier must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, MD 20852.</P>
                <P>(4) In lieu of sending written comments, the Commission invites you to attend one of the public scoping sessions its staff will conduct in the project area, scheduled as follows:</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,r150">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Date and time</CHED>
                        <CHED H="1">Location</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Tuesday, July 21, 2026, 5:00-7:00 p.m. local time</ENT>
                        <ENT>Biosphere 2, 3250 S Biosphere Rd., Oracle, Arizona 85623, 520-621-0436.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wednesday, July 22, 2026, 5:00-7:00 p.m. local time</ENT>
                        <ENT>Central Arizona Community College Signal Peak Campus, 8470 N Overfield Rd., Coolidge, AZ 85128, 520-494-5111.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42432"/>
                        <ENT I="01">Thursday, July 23, 2026, 5:00-7:00 p.m. local time</ENT>
                        <ENT>Buckeye City Hall Satellite Space, 945 N 215th Ave. #137, Buckeye, AZ 85326, 623-349-6000.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tuesday, July 28, 2026, 5:00-7:00 p.m. local time</ENT>
                        <ENT>Willcox Community Center, 312 W Stewart St., Willcox, AZ 85643, 520-766-4211.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wednesday, July 29, 2026, 5:00-7:00 p.m. local time</ENT>
                        <ENT>Mimbres Valley Special Events Center, 2300 E Pine St., Deming, NM 88030, 575-543-6621.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Thursday, July 30, 2026, 5:00-7:00 p.m. local time</ENT>
                        <ENT>Chaparral High School, 800 S County Line Dr., Chaparral, NM 88081, 575-882-2983.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The primary goal of these scoping sessions is to have you identify the specific environmental issues and concerns that should be considered in the environmental document. Individual oral comments will be taken on a one-on-one basis with a court reporter. This format is designed to receive the maximum amount of oral comments in a convenient way during the timeframe allotted.</P>
                <P>
                    Each scoping session is scheduled from 5:00 p.m. to 7:00 p.m. local time. You may arrive at any time after 5:00 p.m. There will not be a formal presentation by Commission staff when the session opens. If you wish to speak, the Commission staff will hand out numbers in the order of your arrival. Comments will be taken until 7:00 p.m. However, if no additional numbers have been handed out and all individuals who wish to provide comments have had an opportunity to do so, staff may conclude the session at 6:30 p.m. Please see appendix 1 for additional information on the session format and conduct.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The appendices referenced in this notice will not appear in the 
                        <E T="04">Federal Register</E>
                        . Copies of the appendices were sent to all those receiving this notice in the mail and are available at 
                        <E T="03">www.ferc.gov</E>
                         using the link called “eLibrary.” For instructions on connecting to eLibrary, refer to the last page of this notice. For assistance, contact FERC at 
                        <E T="03">FERCOnlineSupport@ferc.gov</E>
                         or call toll free, (886) 208-3676 or TTY (202) 502-8659.
                    </P>
                </FTNT>
                <P>Your scoping comments will be recorded by a court reporter (with FERC staff or representative present) and become part of the public record for this proceeding. Transcripts will be publicly available on FERC's eLibrary system (see the last page of this notice for instructions on using eLibrary). If a significant number of people are interested in providing oral comments in the one-on-one settings, a time limit of 5 minutes may be implemented for each commentor.</P>
                <P>
                    <E T="03">It is important to note that the Commission provides equal consideration to all comments received, whether filed in written form or provided orally at a scoping session.</E>
                     Although there will not be a formal presentation, Commission staff will be available throughout the scoping session to answer your questions about the environmental review process. Representatives from Transwestern will also be present to answer project-specific questions.
                </P>
                <P>(5) In lieu of sending written comments or attending an in-person scoping session, the Commission invites you to attend one of the virtual public scoping sessions its staff will conduct by telephone, scheduled as follows:</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,r150">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Date and time</CHED>
                        <CHED H="1">Call-in No.</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Thursday, July 30, 2026, 6:00-8:00 p.m. Mountain Daylight Time</ENT>
                        <ENT>1-866-652-5200, Ask to be joined into the FERC call.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Monday, August 3, 2026, 12:00-2:00 p.m. Mountain Daylight Time</ENT>
                        <ENT>1-866-652-5200, Ask to be joined into the FERC call.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Note that the virtual scoping meetings will start at the times listed above and will terminate once all participants wishing to comment have had the opportunity to do so, or at the above-listed end time, whichever comes first. The primary goal of these scoping sessions is to have you identify the specific environmental issues and concerns that should be considered in the environmental document. Individual oral comments will be taken on a one-on-one basis with a court reporter present on the line. This format is designed to receive the maximum amount of oral comments, in a convenient way during the timeframe allotted.</P>
                <P>There will not be a formal presentation by Commission staff when the session opens. You may call at any time after the session begins, at which time you will be placed on hold. Calls will be answered in the order they are received. Once answered, you will have the opportunity to provide your comment directly to a court reporter with FERC staff or representative present on the line. A time limit of 3 minutes may be implemented for each commentor. Please note that your hold times may vary based on the number of callers at any given time.</P>
                <P>Your oral comments will be recorded by the court reporter and become part of the public record for this proceeding. Transcripts of all comments received during the scoping session(s) will be publicly available on FERC's eLibrary system (see the last page of this notice for instructions on using eLibrary).</P>
                <P>
                    <E T="03">It is important to note that the Commission provides equal consideration to all comments received, whether filed in written form or provided orally at a virtual scoping session.</E>
                </P>
                <P>
                    Additionally, the Commission offers a free service called eSubscription, which makes it easy to stay informed of all issuances and submittals regarding the dockets/projects to which you subscribe. These instant email notifications are the fastest way to receive notification and provide a link to the document files which can reduce the amount of time you spend researching proceedings. Go to 
                    <E T="03">https://www.ferc.gov/ferc-online/overview</E>
                     to register for eSubscription.
                </P>
                <P>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <HD SOURCE="HD1">Summary of the Planned Project</HD>
                <P>
                    Transwestern plans to expand its existing pipeline system by constructing and operating a 48-inch-diameter mainline pipeline, lateral pipelines, compressor stations, meter stations, and other aboveground facilities in Texas, 
                    <PRTPAGE P="42433"/>
                    New Mexico, and Arizona. The Desert Southwest Expansion Project would provide firm transportation service of up to 2.3 billion cubic feet per day (Bcf/d) of natural gas from the Permian Basin to delivery points serving customers in New Mexico and Arizona, and upgrade Transwestern's existing Phoenix Lateral to allow bi-directional flow. According to Transwestern, its project would serve the need for additional natural gas supplies in these states, driven by an increasing demand for reliable natural gas-powered electric generation and natural gas deliveries via Local Distribution Companies.
                </P>
                <P>The Project would consist of the following facilities:</P>
                <P>• 526.5 miles of 48-inch-diameter mainline;</P>
                <P>• 13 lateral pipelines with varying diameters, totaling 181.5 miles;</P>
                <P>• eight new compressor stations;</P>
                <P>• modifications to two existing compressor stations;</P>
                <P>• 26 new meter stations; and</P>
                <P>
                    • valves and pig 
                    <SU>2</SU>
                    <FTREF/>
                     launchers/receivers.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         A “pig” is a tool that the pipeline company inserts into and pushes through the pipeline for cleaning the pipeline, conducting internal inspections, or other purposes.
                    </P>
                </FTNT>
                <P>The general location of the project facilities is shown in appendix 2.</P>
                <HD SOURCE="HD1">Land Requirements for Construction</HD>
                <P>Construction of the Project would require acquisition of temporary construction right-of-way and additional temporary workspace. Transwestern would maintain a portion of the construction right-of-way as permanent right-of-way. To construct the 48-inch diameter mainline, Transwestern would use a 150-foot-wide construction right-of-way and would use between 75 and 90 feet to construct laterals. Specific land requirements (acreages) for construction of the Project will be provided in Transwestern's draft resource reports.</P>
                <HD SOURCE="HD1">NEPA Process and the Environmental Document</HD>
                <P>Any environmental document issued by Commission staff will discuss effects that could occur as a result of the construction and operation of the planned project under the relevant general resource areas:</P>
                <P>• geology and soils;</P>
                <P>• water resources and wetlands;</P>
                <P>• vegetation and wildlife;</P>
                <P>• threatened and endangered species;</P>
                <P>• cultural resources;</P>
                <P>• socioeconomics;</P>
                <P>• land use, recreation, and visual resources;</P>
                <P>• air quality and noise; and</P>
                <P>• reliability and safety.</P>
                <P>Commission staff have already identified several issues that deserve attention based on a preliminary review of the planned facilities and the environmental information provided by Transwestern. This preliminary list of issues may change based on your comments and our analysis:</P>
                <P>• water use by the Project and effects on aquifers;</P>
                <P>• safety and emergency response;</P>
                <P>• light pollution;</P>
                <P>• end uses for the natural gas; and</P>
                <P>• potential effects on:</P>
                <P>○ wilderness areas, the Muleshoe Ranch Cooperative Management Area, the San Pedro River Valley, and other sensitive areas;</P>
                <P>○ threatened and endangered species and migratory birds; and</P>
                <P>○ cultural resources.</P>
                <P>Commission staff will also evaluate reasonable alternatives to the planned project or portions of the project and make recommendations on how to lessen or avoid effects on the various resource areas. Your comments will help Commission staff identify and focus on the issues that might have an effect on the human environment and potentially eliminate others from further study and discussion in the environmental document.</P>
                <P>Although no formal application has been filed, Commission staff have already initiated a NEPA review under the Commission's pre-filing process. The purpose of the pre-filing process is to encourage early involvement of interested stakeholders and to identify and resolve issues before the Commission receives an application. As part of the pre-filing review, Commission staff will contact federal and state agencies to discuss their involvement in the scoping process and the preparation of the environmental document.</P>
                <P>
                    If a formal application is filed, Commission staff will then determine whether to prepare an Environmental Assessment (EA) or an Environmental Impact Statement (EIS). The EA or the EIS will present Commission staff's independent analysis of the environmental issues. If Commission staff prepares an EA, a 
                    <E T="03">Notice of Schedule for the Preparation of an Environmental Assessment</E>
                     will be issued. The EA may be issued for an allotted public comment period. The Commission would consider timely comments on the EA before making its determination on the proposed project. If Commission staff prepares an EIS, a 
                    <E T="03">Notice of Intent to Prepare an EIS/Notice of Schedule</E>
                     will be issued once an application is filed, which will open an additional public comment period. Staff will then prepare a draft EIS that will be issued for public comment. Commission staff will consider all timely comments received during the comment period on the draft EIS, and revise the document, as necessary, before issuing a final EIS. Any EA or draft and final EIS will be available in electronic format in the public record through eLibrary 
                    <SU>3</SU>
                    <FTREF/>
                     and the Commission's natural gas environmental documents web page (
                    <E T="03">https://www.ferc.gov/industries-data/natural-gas/environment/environmental-documents</E>
                    ). If eSubscribed, you will receive instant email notification when the environmental document is issued.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         For instructions on connecting to eLibrary, refer to the last page of this notice.
                    </P>
                </FTNT>
                <P>
                    With this notice, the Commission is asking agencies with jurisdiction by law and/or special expertise with respect to the environmental issues related to this project to formally cooperate in the preparation of the environmental document.
                    <SU>4</SU>
                    <FTREF/>
                     Agencies that would like to request cooperating agency status should follow the instructions for filing comments provided under the 
                    <E T="03">Public Participation</E>
                     section of this notice.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Cooperating agency responsibilities are addressed in Section 107(a)(3) of NEPA (42 U.S. Code 4336(a)(3)).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Consultation Under Section 106 of the National Historic Preservation Act</HD>
                <P>
                    In accordance with the Advisory Council on Historic Preservation's implementing regulations for Section 106 of the National Historic Preservation Act, the Commission is using this notice to initiate consultation with the applicable State Historic Preservation Office(s), and to solicit their views and those of other government agencies, interested Indian tribes, and the public on the project's potential effects on historic properties.
                    <SU>5</SU>
                    <FTREF/>
                     The environmental document for this project will document our findings on the effects on historic properties and summarize the status of consultations under Section 106.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The Advisory Council on Historic Preservation regulations are at Title 36, Code of Federal Regulations, Part 800. Those regulations define historic properties as any prehistoric or historic district, site, building, structure, or object included in or eligible for inclusion in the National Register of Historic Places.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Environmental Mailing List</HD>
                <P>
                    The environmental mailing list includes federal, state, and local government representatives and agencies; elected officials; Native American Tribes; environmental and public interest groups; other interested 
                    <PRTPAGE P="42434"/>
                    parties; and local libraries and media outlets. This list also includes all affected landowners (as defined in the Commission's regulations) who are potential right-of-way grantors, whose property may be used temporarily for project purposes, or who own homes within certain distances of aboveground facilities, and anyone who submits comments on the project and includes a mailing address with their comments. Commission staff will update the environmental mailing list as the analysis proceeds to ensure that Commission notices related to this environmental review are sent to all individuals, organizations, and government entities interested in and/or potentially affected by the planned project.
                </P>
                <P>If you need to make changes to your name/address, or if you would like to remove your name from the mailing list, please complete one of the following steps:</P>
                <P>
                    (1) Send an email to 
                    <E T="03">GasProjectAddressChange@ferc.gov</E>
                     stating your request. You must include the docket number PF26-9-000 in your request. If you are requesting a change to your address, please be sure to include your name and the correct address. If you are requesting to delete your address from the mailing list, please include your name and address as it appeared on this notice. This email address is unable to accept comments.
                </P>
                <P>
                    <E T="03">OR</E>
                </P>
                <P>(2) Return the attached “Mailing List Update Form” (appendix 3).</P>
                <HD SOURCE="HD1">Becoming an Intervenor</HD>
                <P>
                    Once Transwestern files its application with the Commission, you may want to become an “intervenor” which is an official party to the Commission's proceeding. Only intervenors have the right to seek rehearing of the Commission's decision and be heard by the courts if they choose to appeal the Commission's final ruling. An intervenor formally participates in the proceeding by filing a request to intervene pursuant to Rule 214 of the Commission's Rules of Practice and Procedures (18 CFR 385.214). Motions to intervene are more fully described at 
                    <E T="03">https://www.ferc.gov/how-intervene.</E>
                     Please note that the Commission will not accept requests for intervenor status at this time. You must wait until the Commission receives a formal application for the project, after which the Commission will issue a public notice that establishes an intervention deadline.
                </P>
                <HD SOURCE="HD1">Additional Information</HD>
                <P>
                    Additional information about the project is available on the FERC website (
                    <E T="03">www.ferc.gov</E>
                    ) using the eLibrary link. Click on the eLibrary link, click on “General Search” and enter the docket number in the “Docket Number” field. Be sure you have selected an appropriate date range. For assistance, please contact FERC Online Support at 
                    <E T="03">FercOnlineSupport@ferc.gov</E>
                     or toll free at (866) 208-3676, or for TTY, contact (202) 502-8659. The eLibrary link also provides access to the texts of all formal documents issued by the Commission, such as orders, notices, and rulemakings.
                </P>
                <P>
                    Public sessions or site visits will be posted on the Commission's calendar located at 
                    <E T="03">https://www.ferc.gov/news-events/events</E>
                     along with other related information.
                </P>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13880 Filed 7-8-26; 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 #2</SUBJECT>
                <P>Take notice that the Commission received the following exempt wholesale generator filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EG26-269-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Oregon Trail Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Oregon Trail Solar, LLC submits Notice of Self-Certification of Exempt Wholesale Generator Status.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5177.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER10-1585-028; ER15-1754-002; ER15-1747-002; ER10-1594-028; ER16-733-019; ER15-1748-002; ER10-1617-028; ER15-1749-002; ER14-2945-002; ER18-1960-009; ER12-60-030; ER10-1632-030; ER17-554-003; ER10-1628-028; ER10-1626-016.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tenaska Virginia Partners, L.P., Texas Electric Marketing, LLC, Wolf Run Energy LLC, Tenaska Power Services Co., Tenaska Power Management, LLC, Tenaska Pennsylvania Partners, LLC, Roundtop Energy LLC, Oxbow Creek Energy LLC, New Mexico Electric Marketing, LLC, Milan Energy LLC, LQA, LLC, California Electric Marketing, LLC, Beaver Dam Energy LLC, Alpaca Energy LLC, Alabama Electric Marketing, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Alabama Electric Marketing, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5362.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-3407-010; ER23-691-003; ER23-692-003; ER26-1487-001; ER20-2524-001; ER20-2526-001; ER24-2754-002; ER25-1760-001; ER26-1924-001; ER26-384-001; ER23-9-002; ER26-381-001; ER24-1694-001; ER24-1695-001; ER24-1696-001; ER26-382-001; ER26-383-001; ER26-1925-001; ER24-2091-002; ER26-1926-001; ER26-1923-001; ER25-1630-001
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Wakefield BESS 1 LLC, Salem VA BESS 1 LLC, Piney River VA BESS 1 LLC, Paxton BESS 1 LLC, Meadow Creek VA BESS 1 LLC, Ipswich BESS 1 LLC, Holyoke MA BESS 1 LLC, Holden BESS 1 LLC, Groton BESS 2 LLC, Groton BESS 1 LLC, Essex VT BESS 1 LLC, Doc Brown LLC, Danville VA BESS 2 LLC, Colleen VA BESS 1 LLC, Braintree MA BESS 1 LLC, Western Maine Renewables, LLC, Weaver Wind Maine Master Tenant, LLC, Weaver Wind, LLC, Hecate Energy Cider Solar LLC, Hecate Energy Albany 2 LLC, Hecate Energy Albany 1 LLC, Howard Wind LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Howard Wind LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5363.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER17-544-020.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Beacon Solar 1, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Beacon Solar 1, LLC Notice of Change in Category Status with MBR Tariff to be effective 7/7/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5125.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER17-1329-009.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     J.P. Morgan Ventures Energy Corporation.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of J.P. Morgan Ventures Energy Corporation.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5365.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER17-1864-019.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Bayshore Solar A, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Bayshore Solar A, LLC Notice of Change in Category Status with MBR Tariff to be effective 7/7/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5124.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <PRTPAGE P="42435"/>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER17-1871-019.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Bayshore Solar B, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Bayshore Solar B, LLC Notice of Change in Category Status with MBR Tariff to be effective 7/7/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5119.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER17-1909-019.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Bayshore Solar C, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Bayshore Solar C, LLC Notice of Change in Category Status with MBR Tariff to be effective 7/7/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5109.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER18-1150-016; ER22-2187-005; ER22-2188-010.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Northwest Ohio IA, LLC, Northwest Ohio Solar, LLC, Trishe Wind Ohio, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Trishe Wind Ohio, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5366.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-2583-003.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Green River Wind Farm Phase 1, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Green River Wind Farm Phase 1, LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5364.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER20-2755-003; ER11-2335-024; ER19-464-007.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Vermillion Power, L.L.C., Plum Point Services Company, LLC, Caithness Long Island, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region and Notice of Non-Material Change in Status of Caithness Long Island, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5361.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER21-2289-005.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Clover Creek Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Clover Creek Solar, LLC Notice of Change in Category Status with MBR Tariff to be effective 7/7/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5098.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </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>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13884 Filed 7-8-26; 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 #3</SUBJECT>
                <P>Take notice that the Commission received the following electric corporate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC26-121-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Light Energy, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Application for Authorization Under Section 203 of the Federal Power Act of Light Energy, LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260701-5446.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     EC26-122-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     MPH Rockaway Peakers, LLC, Bayswater Peaking Facility, LLC, Jamaica Bay Peaking Facility, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Joint Application for Authorization Under Section 203 of the Federal Power Act of MPH Rockaway Peakers, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260701-5449.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/22/26.
                </P>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER16-1738-021.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Beacon Solar 4, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Beacon Solar 4, LLC Notice of Change in Category Status with MBR Tariff to be effective 7/7/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5131.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER17-306-020.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Beacon Solar 3, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Beacon Solar 3, LLC Notice of Change in Category Status with MBR Tariff to be effective 7/7/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5130.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER20-1385-004; ER22-210-002; ER17-1370-010; ER16-581-011; ER21-2204-004; ER16-2271-010; ER22-1929-002; ER21-1254-004; ER21-1498-003; ER10-3194-009; ER10-3195-010; ER22-1927-002; ER22-1945-001; ER22-1928-001; ER20-1853-003.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Whitehorn Solar LLC, Salt City Solar LLC, Powells Creek Farm Solar, LLC, Sunnybrook Farm Solar, LLC, MATEP Limited Partnership, MATEP LLC, Hawtree Creek Farm Solar, LLC, Genbright LLC, ENGIE Solidago Solar LLC, ENGIE Resources LLC, ENGIE Power &amp; Gas LLC, ENGIE Portfolio Management, LLC, ENGIE Energy Marketing NA, Inc., ENGIE 2020 ProjectCo-NH1 LLC, Bluestone Farm Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Response to 06/26/2026, Deficiency Letter of Bluestone Farm Solar, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260701-5451.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/22/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER21-1488-011.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Luna Storage, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Luna Storage, LLC Notice of Change in Category Status with MBR Tariff to be effective 7/7/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5136.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER21-2156-012.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Antelope Expansion 1B, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Antelope Expansion 1B, LLC Notice of Change in Category Status with MBR Tariff to be effective 7/7/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5134.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER21-2819-006.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     South Field Energy LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Compliance Filing Regarding Effective Date to be effective 10/5/2021.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5162.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER21-2819-007.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     South Field Energy LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Compliance Filing Regarding Effective Date to be effective 7/1/2022.
                    <PRTPAGE P="42436"/>
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5163.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER22-2946-005.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Red Oak Power, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Compliance Filing Regarding Effective Date to be effective 10/1/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5147.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER22-2946-006.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Red Oak Power, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Compliance Filing Regarding Effective Date to be effective 9/1/2023.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5149.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER22-2946-007.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Red Oak Power, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Compliance Filing Regarding Effective Date to be effective 9/1/2023.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5151.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1323-002.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Compliance Filing—Conditional High Impact Large Load Service to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5174.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3086-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Idaho Power Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: RS 185—SWIP-N: GB/IPC TUA Consent &amp; Agreement Matters Letter Agreement to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5110.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3087-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Puget Sound Energy, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Revisions to the Colstrip Real Power Losses Provisions in PSE's OATT to be effective 12/10/2025.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5111.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3088-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     ITC Great Plains, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Filing of Joint Ownership Agreement to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5113.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3089-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Idaho Power Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: RS 186—SWIP—N—GBT/NVE/IPC Consent and Agreement to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5115.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3090-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Municipal Prepaid Energy 2, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Initial Rate Filing: Market-Based Rate Application to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5119.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3091-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Municipal Prepaid Energy 3, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Initial Rate Filing: Market-Based Rate Application to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5122.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3092-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Oregon Trail Solar, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Initial Rate Filing: Application for Market-Based Rate Authorization, Request for Related Waivers to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5142.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3094-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Entergy Louisiana, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: ELL-1803 Elec Coop Transmission Interconnection Agreement to be effective 7/3/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5159.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3095-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Public Service Company of Colorado.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Depreciation Rate—2025 ERC_07.01.26 to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5169.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3096-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Public Service Company of Colorado.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: 2026-07-02 Att O-PSCo to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5182.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3097-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Evergy Missouri West, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Osceola IA to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5185.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3098-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Submission of Tariff Revisions to TCR Shortfall Calculations to be effective 7/6/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5194.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3099-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: 2026-07-06_SA 4797 Entergy LA-Amite Energy Storage GIA (S1076) to be effective 6/30/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5056.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3100-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Great Basin Transmission, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Certificate of Concurrence for Consent and Agreement to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5133.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3101-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Great Basin Transmission, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Certificate of Concurrence for TUA to be effective 9/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5135.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3102-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Cheyenne Light, Fuel and Power Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     205(d) Rate Filing: Filing of LGIA with Black Hills Electric Generation, LLC to be effective 6/22/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5152.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3103-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Duke Energy Indiana, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Notice of Cancellation of Rate Schedule No. 272 to be effective 9/5/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5172.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/27/26.
                </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 
                    <PRTPAGE P="42437"/>
                    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>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13883 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Project No. 4644-017]</DEPDOC>
                <SUBJECT>GR Catalyst Two, LLC ; Notice of Revised Procedural Schedule</SUBJECT>
                <P>Take notice that the schedule for processing the Dahowa Hydroelectric Project No. 4644 final license application has been updated. Subsequent revisions to the schedule may be made as appropriate.</P>
                <GPOTABLE COLS="02" OPTS="L2,nj,tp0,i1" CDEF="s150,xs70">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Milestone</CHED>
                        <CHED H="1">Target date</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Issue Acceptance Letter</ENT>
                        <ENT>September 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Issue Scoping Notice for comments</ENT>
                        <ENT>October 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Issue Notice of Ready for Environmental Analysis</ENT>
                        <ENT>November 2026.</ENT>
                    </ROW>
                </GPOTABLE>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13881 Filed 7-8-26; 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>
                     ER10-2131-033; ER23-2895-004; ER25-3477-001; ER23-2668-005; ER21-258-010.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Todd Solar LLC, Richfield Solar Energy LLC, Pleasant Prairie Solar Energy LLC, Hardin Solar Energy II LLC, Grand Ridge Energy LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Region of Grand Ridge Energy LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5359.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER10-2133-029.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Sheldon Energy LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Sheldon Energy LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5349.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER10-2527-014; ER23-842-005; ER24-3146-002; ER24-3148-002; ER10-2532-022; ER23-1497-005; ER26-711-001; ER24-3149-002; ER20-1610-007; ER23-1595-007; ER10-2535-016; ER23-843-005.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Oak Trail Solar, LLC, Mendota Hills, LLC, LRE Energy Services, LLC, Lone Tree Wind, LLC, Hoosier Line Energy, LLC, Honey Creek Energy, LLC, GSG Wind, LLC, Crescent Ridge LLC, Blackford Wind Energy, LLC, Blackford Solar Energy, LLC, Big Plain Solar, LLC, Allegheny Ridge Wind Farm, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Allegheny Ridge Wind Farm, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5356.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER11-2044-045; ER11-3876-029; ER10-2611-026; ER18-1419-007; ER24-1587-013; ER22-1385-023; ER13-1266-063; ER15-2211-060; ER11-4670-011; ER23-674-019; ER10-1521-029; ER10-1520-029.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Occidental Power Services, Inc., Occidental Power Marketing, L.P., BHE Wind Watch, LLC, NaturEner Power Watch, LLC, MidAmerican Energy Services, LLC, CalEnergy, LLC, BHER Market Operations, LLC., AlbertaEx, L.P., Walnut Ridge Wind, LLC, Saranac Power Partners, L.P., Cordova Energy Company LLC, MidAmerican Energy Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of MidAmerican Energy Company, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5351.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER13-55-028; ER23-2614-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Homer City Generation, L.P., Homer City Generation, L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Motion for Sixty (60) Day Extension of Time to submit Triennial Market Power Update of Homer City Generation, L.P.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5290.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER13-1910-006; ER16-1018-005; ER20-2771-004.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Guzman Western Slope LLC, Guzman Renewable Energy Partners LLC, Guzman Power Markets.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Guzman Power Markets, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5346.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER14-2102-005.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Danskammer Energy, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Danskammer Energy, LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5291.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER14-2102-006.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Danskammer Energy, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Danskammer Energy, LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5347.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER14-2187-027; ER21-2137-015.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     IR Energy Management LLC, Grand Ridge Energy Storage LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Grand Ridge Energy Storage LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5352.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER15-356-017; ER15-357-017.
                    <PRTPAGE P="42438"/>
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Chief Keystone Power, LLC, Chief Conemaugh Power, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Chief Conemaugh Power, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5345.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER15-1905-023.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     AZ721 LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Amazon Energy LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5342.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER15-2013-018; ER12-2510-015; ER15-2014-012; ER25-3260-002; ER17-256-024; ER22-1566-007; ER12-2512-015; ER17-243-023; ER19-481-008; ER18-2252-007; ER15-2022-011; ER17-1847-002; ER15-2026-011; ER23-2941-002; ER23-2943-002; ER17-245-023.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Waterford Power, LLC, Talen Keystone LLC, Talen Conemaugh LLC, Susquehanna Nuclear, LLC, Moxie Freedom LLC, Montour, LLC, MC Project Company LLC, LMBE Project Company LLC, Lawrenceburg Power, LLC, H.A. Wagner LLC, Guernsey Power Station LLC, Darby Power, LLC, Lightstone Marketing LLC, Brunner Island, LLC, Brandon Shores LLC, Talen Energy Marketing, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Talen Energy Marketing, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5357.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER17-1663-004; ER22-296-003.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Jackson Generation, LLC, Elwood Energy LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Elwood Energy LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5288.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-106-010; ER12-1725-010.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     ECP Energy I, LLC, Liberty Electric Power, LLC, Empire Generating Co, LLC, Dighton Power, LLC, EquiPower Resources Management, LLC, Lake Road Generating Company, L.P., MASSPOWER, Milford Power Company, LLC, Red Oak Power, LLC, Birdsboro Power LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Birdsboro Power LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5348.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER19-2462-015; ER18-2264-017; ER13-1485-015; ER10-3253-015; ER19-461-006; ER14-1777-013; ER18-1310-006; ER10-3240-015; ER15-2722-011; ER10-3239-015.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Wheelabrator Westchester L.P., Wheelabrator Saugus Inc., Wheelabrator North Andover Inc., Wheelabrator Millbury Inc., Wheelabrator Falls Inc., Wheelabrator Concord Company, L.P., Wheelabrator Bridgeport, L.P., Wheelabrator Baltimore, L.P., Macquarie Energy Trading LLC, Macquarie Energy LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Macquarie Energy LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5358.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER23-66-004; ER25-3399-002; ER20-2202-005; ER20-2032-004; ER10-2834-010; ER23-139-005; ER17-1438-005; ER25-2713-001; ER23-1494-003; ER23-1493-003; ER23-1501-004; ER24-832-003; ER25-3456-001; ER20-2671-008; ER23-138-004; ER12-1329-011; ER24-153-001; ER24-1231-003.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Wythe County Solar Project, LLC, Willowbrook Solar I, LLC, Wildcat Wind Farm I, LLC, Watlington Solar, LLC, Water Strider Solar, LLC, Union Ridge Solar, LLC, RWE Trading Americas Inc., RWE Supply &amp; Trading Americas, LLC, RWE Clean Energy Wholesale Services, Inc., RWE Clean Energy Solutions, Inc., RWE Clean Energy QSE, LLC, Radford's Run Wind Farm, LLC, Pleasant Hill Solar, LLC, Munnsville Wind Farm, LLC, Hardin Wind LLC, Cassadaga Wind LLC, Baron Winds II LLC, Baron Winds LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Baron Winds LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5293.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER24-1386-005; ER19-2460-006; ER24-2534-005; ER24-2535-005; ER22-123-007.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Hecate Energy Highland LLC, Gravel Pit Solar IV, LLC, Gravel Pit Solar III, LLC, DWW Solar II, LLC, Bartonsville Energy Facility, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Bartonsville Energy Facility, LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5289.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/28/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-621-001; ER22-1999-006.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Number Three Wind LLC, Alle-Catt Wind Energy LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Triennial Market Power Analysis for Northeast Region of Alle-Catt Wind Energy LLC, et al.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/30/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260630-5354.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 8/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-3093-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Northwest Power Pool d/b/a Western Power Pool.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Petition for Limited Waiver of Northwest Power Pool d/b/a Western Power Pool.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     6/29/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260629-5292.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </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>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13885 Filed 7-8-26; 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 and Accounting Request filings:</P>
                <HD SOURCE="HD1">Filings Instituting Proceedings</HD>
                <P>
                    <E T="03">Docket Numbers:</E>
                     AC26-95-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Jayhawk Pipeline, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Jayhawk Pipeline, L.L.C. submits notification of premature destruction of records due to a natural disaster.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                    <PRTPAGE P="42439"/>
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5178.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     PR26-70-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     UGI Utilities, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     284.123 Rate Filing: Rate Election Effective July 2026 Corrected TOFC to be effective 7/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5098.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/23/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-965-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Iroquois Gas Transmission System, L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: 7.2.26 Negotiated Rates—J. Aron &amp; Company LLC H-7130-89 to be effective 7/2/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5002.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/14/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-966-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Spire MoGas Pipeline LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Penalty Revenue Crediting Report of Spire MoGas Pipeline LLC.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/1/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260701-5409.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/13/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-968-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     NEXUS Gas Transmission, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: Tariff Contact Update to be effective 8/2/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5112.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/14/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-969-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Natural Gas Pipeline Company of America LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: Amendment to a Negotiated Rate Agreement Filing—to be effective 7/3/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5114.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/14/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-970-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Big Sandy Pipeline, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: Tariff Contact Update to be effective 8/2/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5116.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/14/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-971-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Mountain Valley Pipeline, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: Negotiated Rate Capacity Release Agreement—7/3/2026 to be effective 7/3/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/2/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260702-5147.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/14/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-972-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Equitrans, L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     4(d) Rate Filing: Negotiated Rate Capacity Release Agreement—7/3/2026 to be effective 7/3/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     7/6/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260706-5054.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 7/20/26.
                </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>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Debbie-Anne A. Reese,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13882 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OLEM-2026-3268; FRL-13357-01-OLEM]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed Information Collection Request; Comment Request: Technical Assistance Needs Assessments (TANAs) at Superfund Remedial or Removal Sites</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), “Technical Assistance Needs Assessments (TANAs) at Superfund Remedial or Removal Sites” (EPA ICR No. 2470.04, OMB Control No. 2050-0211) to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act (PRA). Before doing so, EPA is soliciting public comments on specific aspects of the proposed information collection as described below. This is a proposed renewal of the existing ICR, which is currently approved through March 31, 2027. This document allows for 60 days for public comments.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, referencing Docket ID No. EPA-HQ-OLEM-2026-3268. Send comments to EPA online: 
                        <E T="03">https://www.regulations.gov</E>
                         (our preferred method), by email to: 
                        <E T="03">foster.john@epa.gov;</E>
                         or by mail to: EPA Docket Center, Environmental Protection Agency, Mail Code 28221T, 1200 Pennsylvania Ave. NW, Washington, DC 20460. 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 (CBI) or other information whose disclosure is restricted by statute.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        John Foster; Partnerships and Community Involvement Branch; Office of Superfund Remediation and Emergency Response; Environmental Protection Agency; Mail Code 5204T; 1200 Pennsylvania Ave. NW, Washington, DC 20460-0001; telephone number: (202) 566-2870; email address: 
                        <E T="03">foster.john@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 March 31, 2027. 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 document 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">https://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">https://www.epa.gov/dockets.</E>
                </P>
                <P>
                    Pursuant to section 3506(c)(2)(A) of the PRA, EPA is soliciting comments and information to enable it to: (i) evaluate whether the proposed collection of information is necessary 
                    <PRTPAGE P="42440"/>
                    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. 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, EPA will issue another 
                    <E T="04">Federal Register</E>
                     document 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>
                     This information collection request pertains to the use of “Technical Assistance Needs Assessments” (TANAs) to solicit feedback from members of the affected community in order to determine how the community is receiving technical information about a Superfund remedial site (contaminant cleaned up/treated onsite) or removal site (contaminant removed and cleaned up/treated offsite); whether the community requires additional assistance in order to understand and respond to site-related technical information; and whether there are organizations in the community that are interested or involved in site-related issues and capable of acting as an appropriate conduit for technical assistance services to the affected community. EPA estimates that for each TANA it conducts, 20 individuals are interviewed, per site, via direct face-to-face interaction, phone, or virtual call at five sites, with an approximate total of 100 individuals interviewed each year. Responses to the collection of information are voluntary and the names of respondents will be protected by the Privacy Act. The information obtained from each TANA will help ensure the community's needs for technical information assistance are defined as early in the remedial or removal process as possible and enable meaningful community involvement in the Superfund decision-making process. Additionally, the TANA process produces a blueprint for designing a coordinated effort to meet the community's needs for additional technical assistance while minimizing the overlap of services provided. The burden estimates, numbers and types of respondents, wage rates, as well as unit and total costs for this ICR renewal will be revised and updated if needed during the 60-day comment period while the ICR Supporting Statement is undergoing review at OMB.
                </P>
                <P>
                    <E T="03">Form numbers:</E>
                     None.
                </P>
                <P>
                    <E T="03">Respondents/affected entities:</E>
                     Respondents to this ICR are local, state, and Tribal government officials, representatives of potentially responsible party (PRP) (PRPs are individuals, companies, or any other party that are potentially liable for payment of Superfund cleanup costs), community organizations, businesses and individuals who may be impacted by a Superfund site or a removal action lasting 120 days or longer. These community members voluntarily participate in community involvement activities throughout the remedial phase of the Superfund process. Respondents are categorized using the National American Industry Classification Codes (NAICS), which are the standard classification used by Federal statistical agencies in classifying businesses, government and others for the purpose of collecting, analyzing, and publishing statistical data related to U.S. business and the economy. NAICS six-digit coding system identifies industries and non-industry categories. For example, local/state governments are categorized under the first two of the six digits as Sector 92: Public Administration. Several 3rd digit subsectors are relevant to remedial cleanup actions, community involvement, and site redevelopment, and they include: Subsector 924, Administration of Environmental Quality Programs; Subsector 925, Administration of Housing Programs, Urban Planning and Community Development; and Subsector 926, Administration of Economic Programs. Residents/community members/private households fall under NAICS code 814110; community &amp; civic organizations fall under 813410.
                </P>
                <P>
                    <E T="03">Respondent's obligation to respond:</E>
                     Voluntary.
                </P>
                <P>
                    <E T="03">Estimated number of respondents:</E>
                     100 (total) (20 per TANA at five sites).
                </P>
                <P>
                    <E T="03">Frequency of response:</E>
                     Once during either a removal cleanup lasting 120 days or longer or a remedial cleanup of a site. Each TANA interview is expected to last approximately one (1) hour in duration.
                </P>
                <P>
                    <E T="03">Total estimated burden:</E>
                     100 hours (per year). Burden is defined at 5 CFR 1320.03(b).
                </P>
                <P>
                    <E T="03">Total estimated cost:</E>
                     $2,587 (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 the number of hours in the total estimated respondent burden compared with the ICR currently approved by OMB.
                </P>
                <SIG>
                    <NAME>Mark Barolo,</NAME>
                    <TITLE>Director, Office of Superfund and Emergency Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13849 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[EPA-HQ-OW-2026-4852; FRL-13454-01-OW]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed Information Collection Request; Comment Request; EPA Program Information on Source Water Protection (Renewal)</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 (EPA) is planning to submit an information collection request (ICR), EPA Program Information on Source Water Protection (Renewal) (EPA ICR Number 1816.09, OMB Control Number 2040-0197) to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act. Before doing so, 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 September 30, 2026. This notice allows for 60 days for public comments.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments, referencing Docket ID Number EPA-HQ-OW-2026-4852 to EPA online using 
                        <E T="03">www.regulations.gov</E>
                         (our preferred method), by email to 
                        <E T="03">OW-Docket@epa.gov</E>
                         or by mail to: EPA Docket Center, Environmental Protection Agency, Mail Code 28221T, 1200 Pennsylvania Ave. NW, Washington, DC 20460. 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 (CBI) or other information whose disclosure is restricted by statute.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Laura Montoya, Drinking Water Capacity and Compliance Assistance Division, Office of Groundwater and Drinking Water, MC 4606M, 
                        <PRTPAGE P="42441"/>
                        Environmental Protection Agency, 1200 Pennsylvania Ave. NW, Washington, DC 20460; telephone number: 202-564-2202; email address: 
                        <E T="03">montoya.laura@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 September 30, 2026. 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 Paperwork Reduction Act (PRA), 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. 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, 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>
                     EPA is collecting data from the states on their advancement toward substantial implementation of source water protection strategies for all community water systems (CWSs). EPA and states use this voluntary collection of data to track and understand the progress toward increasing the percentage of CWSs (and the populations they serve) where risk is minimized through source water protection. Source water protection data that states submit directly to the Safe Drinking Water Information System (SDWIS) is accessible to the public via EPA's website at: 
                    <E T="03">https://www.epa.gov/ground-water-and-drinking-water/safe-drinking-water-information-system-sdwis-federal-reporting.</E>
                     Availability of this information, together with source water and demographic indicators that are publicly available via EPA's Drinking Water Mapping Application to Protect Source Waters (DWMAPS) on EPA's website at: 
                    <E T="03">https://www.epa.gov/sourcewaterprotection/drinking-water-mapping-application-protect-source-waters-dwmaps,</E>
                     empowers communities to include these considerations in their own analyses and outreach efforts.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     None.
                </P>
                <P>
                    <E T="03">Respondents/affected entities:</E>
                     51.
                </P>
                <P>
                    <E T="03">Respondent's obligation to respond:</E>
                     Voluntary.
                </P>
                <P>
                    <E T="03">Estimated number of respondents:</E>
                     51 (total).
                </P>
                <P>
                    <E T="03">Frequency of response:</E>
                     Annual.
                </P>
                <P>
                    <E T="03">Total estimated burden:</E>
                     102 hours annually. Burden is defined at 5 CFR 1320.03(b).
                </P>
                <P>
                    <E T="03">Total estimated cost:</E>
                     EPA estimates that, over the three years covered by this request, the total respondent burden associated with this reporting will average 102 hours per year and the cost to respondents of the information collection will average $6,608 per year.
                </P>
                <P>
                    <E T="03">Changes in the Estimates:</E>
                     EPA estimates there will be a decrease in the total estimated respondent burden compared with the ICR currently approved by OMB. This decrease is anticipated because all states will report source water protection data directly to the Safe Drinking Water Information System, decreasing the previous burden of reporting information to EPA Regional contacts via email. Additionally, state databases are fully developed and tracking is routine, which EPA believes will minimize hourly burden and cost for states.
                </P>
                <SIG>
                    <NAME>Jennifer L. McLain,</NAME>
                    <TITLE>Director, Office Ground Water &amp; Drinking Water.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13902 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Proposed Agency Information Collection Activities; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice, request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Board of Governors of the Federal Reserve System (Board) invites comment on a proposal to extend for three years, with revision, the Applications for Employment with the Board of Governors of the Federal Reserve System (FR 28; OMB No. 7100-0181).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by FR 28, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Agency Website: https://www.federalreserve.gov/apps/proposals/.</E>
                         Follow the instructions for submitting comments, including attachments. 
                        <E T="03">Preferred Method.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Benjamin W. McDonough, Secretary, Board of Governors of the Federal Reserve System, 20th Street and Constitution Avenue NW, Washington, DC 20551.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Same as mailing address.
                    </P>
                    <P>
                        • 
                        <E T="03">Other Means: publiccomments@frb.gov.</E>
                         You must include the OMB number or the FR number in the subject line of the message.
                    </P>
                    <P>
                        Comments received are subject to public disclosure. In general, comments received will be made available on the Board's website at 
                        <E T="03">https://www.federalreserve.gov/apps/proposals/</E>
                         without change and will not be modified to remove personal or business information including confidential, contact, or other identifying information. Comments should not include any information such as confidential information that would not be appropriate for public disclosure. Public comments may also be viewed electronically or in person in Room M-4365A, 2001 C St. NW, Washington, DC 20551, between 9 a.m. and 5 p.m. during Federal business weekdays.
                    </P>
                    <P>Additionally, commenters may send a copy of their comments to the Office of Management and Budget (OMB) Desk Officer for the Federal Reserve Board, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 10235, 725 17th Street NW, Washington, DC 20503, or by fax to (202) 395-6974.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Federal Reserve Board Clearance Officer—Nuha Elmaghrabi—Office of the Chief Data Officer, Board of Governors of the Federal Reserve System, 
                        <E T="03">nuha.elmaghrabi@frb.gov,</E>
                         (202) 452-3884.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On June 15, 1984, OMB delegated to the Board authority under the Paperwork 
                    <PRTPAGE P="42442"/>
                    Reduction Act (PRA) to approve and assign OMB control numbers to collections of information conducted or sponsored by the Board. In exercising this delegated authority, the Board is directed to take every reasonable step to solicit comment. In determining whether to approve a collection of information, the Board will consider all comments received from the public and other agencies.
                </P>
                <P>
                    During the comment period for this proposal, a copy of the proposed PRA OMB submission, including the draft reporting form and instructions, supporting statement (which contains more detail about the information collection and burden estimates than this notice), and other documentation, will be made available on the Board's public website at 
                    <E T="03">https://www.federalreserve.gov/apps/reportingforms/review</E>
                     or may be requested from the agency clearance officer, whose name appears above. On the page displayed at the link above, you can find the supporting information by referencing the collection identifier, FR 28. Final versions of these documents will be made available at 
                    <E T="03">https://www.reginfo.gov/public/do/PRAMain,</E>
                     if approved.
                </P>
                <HD SOURCE="HD1">Request for Comment on Information Collection Proposal</HD>
                <P>The Board invites public comment on the following information collections, which are being reviewed under authority delegated by the OMB under the PRA. Comments are invited on the following:</P>
                <P>a. Whether the proposed collections of information are necessary for the proper performance of the Board's functions, including whether the information has practical utility;</P>
                <P>b. The accuracy of the Board's estimate of the burden of the proposed information collections, including the validity of the methodology and assumptions used;</P>
                <P>c. Ways to enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>d. Ways to minimize the burden of information collection on respondents, including through the use of automated collection techniques or other forms of information technology; and</P>
                <P>e. Estimates of capital or startup costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <P>At the end of the comment period, the comments and recommendations received will be analyzed to determine the extent to which the Board should modify the proposal.</P>
                <HD SOURCE="HD1">Proposal Under OMB Delegated Authority To Extend for Three Years, With Revision, the Following Information Collections</HD>
                <P>
                    <E T="03">Collection title:</E>
                     Applications for Employment with the Board of Governors of the Federal Reserve System.
                </P>
                <P>
                    <E T="03">Collection identifier:</E>
                     FR 28.
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0181.
                </P>
                <P>
                    <E T="03">General description of collection:</E>
                     The FR 28 consists of the following information collections:
                </P>
                <P>The Application for Employment (FR 28a), which collects information to determine the qualifications of applicants for employment with the Board (such as education and training, employment records, and other general background information since the time the applicant left high school), the Applicant's Voluntary Self-Identification (FR 28s), which is an optional form that collects information on the applicant's sex, race, and ethnicity, the Research Assistant Application (FR 28i), which collects contact information, information on a Research Assistant (RA) applicant's level of interest in various economic topics and experience in different data analytics/programs, and application documentation (including resume, cover letter, transcripts, and letter(s) of recommendation), the Pre-Hire Conflict of Interest Screening Form (FR 28c), which collects information from external applicants after they have been selected for an interview at the Board regarding certain financial interests that could pose a conflict of interest based on the Board's supplemental ethics regulations and/or the duties of the position for which they are applying, and the Reference Check Form (FR 28r), which captures information from professional references when the Board conducts reference checks for external applicants who have received a verbal offer of employment.</P>
                <P>
                    <E T="03">Proposed revisions:</E>
                     The Board proposes to revise the FR 28 by changing the collection platform of the FR 28a and FR 28s from Taleo to Workday, which will allow for three new submission methods in the Workday system (applying through LinkedIn, applying with resume parsing, and applying with previous application); the FR 28c, which is currently sent out via email, will also transition into Workday. The platform change will result in several data field changes for the FR 28a to 1) align with the configuration of Workday as the Board's new applicant tracking system (ATS) and 2) remove fields that are no longer necessary. These changes would be effective 30 days after the publication of the final 
                    <E T="04">Federal Register</E>
                     notice. By Fall 2028, the FR 28i will also be transitioned from ServiceNow to Workday. Before the transition of the FR 28i into Workday, one additional data field will be added in order to link applicants between ServiceNow and Workday; once the FR 28i is also in Workday, the data field will be removed. There are no proposed changes to the FR 28r as part of this clearance.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Event-generated.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals seeking employment with the Board.
                </P>
                <P>
                    <E T="03">Total estimated number of respondents:</E>
                     FR 28a (LinkedIn), 14,076; FR 28a (Resume Parsing), 18,098; FR 28a (Manual Application), 4,021; FR 28a (Use Last Application), 4,021; FR 28a (Interview Selection), 1,129; FR 28a (PDF), 238; FR 28s, 40,216; FR 28i, 800; FR 28c, 1,547; and FR 28r, 273.
                </P>
                <P>
                    <E T="03">Estimated average hours per response:</E>
                     FR 28a (LinkedIn), 0.46; FR 28a (Resume Parsing), 0.44; FR 28a (Manual Application), 0.69; FR 28a (Use Last Application), 0.26; FR 28a (Interview Selection), 0.71; FR 28a (PDF), 1.69; FR 28s, 0.02; FR 28i, 0.91; FR 28c, 0.62; and FR 28r, 0.34.
                </P>
                <P>
                    <E T="03">Total estimated change in burden:</E>
                     (1,950).
                </P>
                <P>
                    <E T="03">Total estimated annual burden hours:</E>
                     22,045.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Erin M. Cayce,</NAME>
                    <TITLE>Assistant Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13856 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Proposed Agency Information Collection Activities; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice, request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Board of Governors of the Federal Reserve System (Board) invites comment on a proposal to extend for three years, with revision, the Ongoing Intermittent Survey of Households (FR 3016; OMB No. 7100-0150).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by FR 3016, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Agency Website: https://www.federalreserve.gov/apps/proposals/</E>
                        . Follow the instructions for 
                        <PRTPAGE P="42443"/>
                        submitting comments, including attachments. 
                        <E T="03">Preferred Method</E>
                        .
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Benjamin W. McDonough, Secretary, Board of Governors of the Federal Reserve System, 20th Street and Constitution Avenue NW, Washington, DC 20551.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Same as mailing address.
                    </P>
                    <P>
                        • 
                        <E T="03">Other Means: publiccomments@frb.gov</E>
                        . You must include the OMB number or the FR number in the subject line of the message.
                    </P>
                    <P>
                        Comments received are subject to public disclosure. In general, comments received will be made available on the Board's website at 
                        <E T="03">https://www.federalreserve.gov/apps/proposals/</E>
                         without change and will not be modified to remove personal or business information including confidential, contact, or other identifying information. Comments should not include any information such as confidential information that would not be appropriate for public disclosure. Public comments may also be viewed electronically or in person in Room M-4365A, 2001 C St. NW, Washington, DC 20551, between 9 a.m. and 5 p.m. during Federal business weekdays.
                    </P>
                    <P>Additionally, commenters may send a copy of their comments to the Office of Management and Budget (OMB) Desk Officer for the Federal Reserve Board, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 10235, 725 17th Street NW, Washington, DC 20503, or by fax to (202) 395-6974.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Federal Reserve Board Clearance Officer—Nuha Elmaghrabi—Office of the Chief Data Officer, Board of Governors of the Federal Reserve System, 
                        <E T="03">nuha.elmaghrabi@frb.gov,</E>
                         (202) 452-3884.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On June 15, 1984, OMB delegated to the Board authority under the Paperwork Reduction Act (PRA) to approve and assign OMB control numbers to collections of information conducted or sponsored by the Board. In exercising this delegated authority, the Board is directed to take every reasonable step to solicit comment. In determining whether to approve a collection of information, the Board will consider all comments received from the public and other agencies.</P>
                <P>
                    During the comment period for this proposal, a copy of the proposed PRA OMB submission, including the draft reporting form and instructions, supporting statement (which contains more detail about the information collection and burden estimates than this notice), and other documentation, will be made available on the Board's public website at 
                    <E T="03">https://www.federalreserve.gov/apps/reportingforms/review</E>
                     or may be requested from the agency clearance officer, whose name appears above. On the page displayed at the link above, you can find the supporting information by referencing the collection identifier, FR 3016. Final versions of these documents will be made available at 
                    <E T="03">https://www.reginfo.gov/public/do/PRAMain,</E>
                     if approved.
                </P>
                <HD SOURCE="HD1">Request for Comment on Information Collection Proposal</HD>
                <P>The Board invites public comment on the following information collection, which is being reviewed under authority delegated by the OMB under the PRA. Comments are invited on the following:</P>
                <P>a. Whether the proposed collection of information is necessary for the proper performance of the Board's functions, including whether the information has practical utility;</P>
                <P>b. The accuracy of the Board's estimate of the burden of the proposed information collection, including the validity of the methodology and assumptions used;</P>
                <P>c. Ways to enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>d. Ways to minimize the burden of information collection on respondents, including through the use of automated collection techniques or other forms of information technology; and</P>
                <P>e. Estimates of capital or startup costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <P>At the end of the comment period, the comments and recommendations received will be analyzed to determine the extent to which the Board should modify the proposal.</P>
                <HD SOURCE="HD1">Proposal Under OMB Delegated Authority To Extend for Three Years, With Revision, the Following Information Collection</HD>
                <P>
                    <E T="03">Collection title:</E>
                     Ongoing Intermittent Survey of Households.
                </P>
                <P>
                    <E T="03">Collection identifier:</E>
                     FR 3016.
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0150.
                </P>
                <P>
                    <E T="03">General description of collection:</E>
                     The Ongoing Intermittent Survey of Households, the FR 3016, is a voluntary survey used to study consumer financial decisions, attitudes, and payment behavior. The survey data have helped the Board understand consumer credit markets and consumer behavior.
                </P>
                <P>
                    <E T="03">Proposed revisions:</E>
                     The Board proposes to revise the FR 3016 to reflect a change in the survey instrument from phone interviews to a web questionnaire and an increase in the sample size from approximately 600 to 1,150 households. The proposed revisions will be effective immediately.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Monthly.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals.
                </P>
                <P>
                    <E T="03">Total estimated number of respondents:</E>
                     1,150.
                </P>
                <P>
                    <E T="03">Total estimated change in burden:</E>
                     216 hours.
                </P>
                <P>
                    <E T="03">Total estimated annual burden hours:</E>
                     415.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Erin M. Cayce,</NAME>
                    <TITLE>Assistant Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13905 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Proposed Agency Information Collection Activities; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice, request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Board of Governors of the Federal Reserve System (Board) invites comment on a proposal to extend for three years, without revision, the Survey of Household Economics and Decisionmaking (FR 3077; OMB No. 7100-0374).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by FR 3077, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Agency Website: https://www.federalreserve.gov/apps/proposals/</E>
                        . Follow the instructions for submitting comments, including attachments. 
                        <E T="03">Preferred Method</E>
                        .
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Benjamin W. McDonough, Secretary, Board of Governors of the Federal Reserve System, 20th Street and Constitution Avenue NW, Washington, DC 20551.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Same as mailing address.
                    </P>
                    <P>
                        • 
                        <E T="03">Other Means: publiccomments@frb.gov</E>
                        . You must include the OMB number or the FR number in the subject line of the message.
                    </P>
                    <P>
                        Comments received are subject to public disclosure. In general, comments received will be made available on the Board's website at 
                        <E T="03">https://www.federalreserve.gov/apps/proposals/</E>
                         without change and will not be modified to remove personal or 
                        <PRTPAGE P="42444"/>
                        business information including confidential, contact, or other identifying information. Comments should not include any information such as confidential information that would not be appropriate for public disclosure. Public comments may also be viewed electronically or in person in Room M-4365A, 2001 C St. NW, Washington, DC 20551, between 9 a.m. and 5 p.m. during Federal business weekdays.
                    </P>
                    <P>Additionally, commenters may send a copy of their comments to the Office of Management and Budget (OMB) Desk Officer for the Federal Reserve Board, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 10235, 725 17th Street NW, Washington, DC 20503, or by fax to (202) 395-6974.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Federal Reserve Board Clearance Officer—Nuha Elmaghrabi—Office of the Chief Data Officer, Board of Governors of the Federal Reserve System, 
                        <E T="03">nuha.elmaghrabi@frb.gov,</E>
                         (202) 452-3884.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On June 15, 1984, OMB delegated to the Board authority under the Paperwork Reduction Act (PRA) to approve and assign OMB control numbers to collections of information conducted or sponsored by the Board. In exercising this delegated authority, the Board is directed to take every reasonable step to solicit comment. In determining whether to approve a collection of information, the Board will consider all comments received from the public and other agencies.</P>
                <P>
                    During the comment period for this proposal, a copy of the proposed PRA OMB submission, including the draft reporting form and instructions, supporting statement (which contains more detail about the information collection and burden estimates than this notice), and other documentation, will be made available on the Board's public website at 
                    <E T="03">https://www.federalreserve.gov/apps/reportingforms/review</E>
                     or may be requested from the agency clearance officer, whose name appears above. On the page displayed at the link above, you can find the supporting information by referencing the collection identifier, FR 3077. Final versions of these documents will be made available at 
                    <E T="03">https://www.reginfo.gov/public/do/PRAMain,</E>
                     if approved.
                </P>
                <HD SOURCE="HD1">Request for Comment on Information Collection Proposal</HD>
                <P>The Board invites public comment on the following information collection, which is being reviewed under authority delegated by the OMB under the PRA. Comments are invited on the following:</P>
                <P>a. Whether the proposed collection of information is necessary for the proper performance of the Board's functions, including whether the information has practical utility;</P>
                <P>b. The accuracy of the Board's estimate of the burden of the proposed information collection, including the validity of the methodology and assumptions used;</P>
                <P>c. Ways to enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>d. Ways to minimize the burden of information collection on respondents, including through the use of automated collection techniques or other forms of information technology; and</P>
                <P>e. Estimates of capital or startup costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <P>At the end of the comment period, the comments and recommendations received will be analyzed to determine the extent to which the Board should modify the proposal.</P>
                <HD SOURCE="HD1">Proposal Under OMB Delegated Authority To Extend for Three Years, Without Revision, the Following Information Collection</HD>
                <P>
                    <E T="03">Collection title:</E>
                     Survey of Household Economics and Decisionmaking.
                </P>
                <P>
                    <E T="03">Collection identifier:</E>
                     FR 3077.
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0374.
                </P>
                <P>
                    <E T="03">General description of collection:</E>
                     The Survey of Household Economics and Decisionmaking (SHED) is an ad hoc voluntary survey covering topics such as individuals' overall financial well-being, employment experiences, income and ability to pay bills, economic preparedness, banking and access to credit, housing and living arrangement decisions, education and human capital, student loans, and retirement planning. The overall content of the SHED depends on changing economic developments as well as changes in the financial services industry. The Board uses the SHED to monitor usage of emerging financial products and understand how macroeconomic conditions are affecting households.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Annually.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Non-institutionalized individuals who are 18 years of age and older.
                </P>
                <P>
                    <E T="03">Total estimated number of respondents:</E>
                     12,500.
                </P>
                <P>
                    <E T="03">Total estimated annual burden hours:</E>
                     7,500.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Erin M. Cayce,</NAME>
                    <TITLE>Assistant Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13908 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Proposed Agency Information Collection Activities; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice, request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Board of Governors of the Federal Reserve System (Board) invites comment on a proposal to extend for three years, with revision, the Ad Hoc Clearance for Board-Wide Use (FR 3100; OMB No. 7100-0385).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by FR 3100, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Agency Website: https://www.federalreserve.gov/apps/proposals/.</E>
                         Follow the instructions for submitting comments, including attachments. 
                        <E T="03">Preferred Method.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Benjamin W. McDonough, Secretary and Ombuds, Board of Governors of the Federal Reserve System, 20th Street and Constitution Avenue NW, Washington, DC 20551.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Same as mailing address.
                    </P>
                    <P>
                        • 
                        <E T="03">Other Means: publiccomments@frb.gov.</E>
                         You must include the OMB number or the FR number in the subject line of the message.
                    </P>
                    <P>
                        Comments received are subject to public disclosure. In general, comments received will be made available on the Board's website at 
                        <E T="03">https://www.federalreserve.gov/apps/proposals/</E>
                         without change and will not be modified to remove personal or business information including confidential, contact, or other identifying information. Comments should not include any information such as confidential information that would not be appropriate for public disclosure. Public comments may also be viewed electronically or in person in Room M-4365A, 2001 C St. NW, Washington, DC 20551, between 9 a.m. and 5 p.m. during Federal business weekdays.
                    </P>
                    <P>
                        Additionally, commenters may send a copy of their comments to the Office of Management and Budget (OMB) Desk 
                        <PRTPAGE P="42445"/>
                        Officer for the Federal Reserve Board, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 10235, 725 17th Street NW, Washington, DC 20503, or by fax to (202) 395-6974.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Federal Reserve Board Clearance Officer—Nuha Elmaghrabi—Office of the Chief Data Officer, Board of Governors of the Federal Reserve System, 
                        <E T="03">nuha.elmaghrabi@frb.gov,</E>
                         (202) 452-3884.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On June 15, 1984, OMB delegated to the Board authority under the Paperwork Reduction Act (PRA) to approve and assign OMB control numbers to collections of information conducted or sponsored by the Board. In exercising this delegated authority, the Board is directed to take every reasonable step to solicit comment. In determining whether to approve a collection of information, the Board will consider all comments received from the public and other agencies.</P>
                <P>
                    During the comment period for this proposal, a copy of the proposed PRA OMB submission, including the draft reporting form and instructions, supporting statement (which contains more detail about the information collection and burden estimates than this notice), and other documentation, will be made available on the Board's public website at 
                    <E T="03">https://www.federalreserve.gov/apps/reportingforms/review</E>
                     or may be requested from the agency clearance officer, whose name appears above. On the page displayed at the link above, you can find the supporting information by referencing the collection identifier, FR 3100. Final versions of these documents will be made available at 
                    <E T="03">https://www.reginfo.gov/public/do/PRAMain,</E>
                     if approved.
                </P>
                <HD SOURCE="HD1">Request for Comment on Information Collection Proposal</HD>
                <P>The Board invites public comment on the following information collection, which is being reviewed under authority delegated by the OMB under the PRA. Comments are invited on the following:</P>
                <P>a. Whether the proposed collection of information is necessary for the proper performance of the Board's functions, including whether the information has practical utility;</P>
                <P>b. The accuracy of the Board's estimate of the burden of the proposed information collection, including the validity of the methodology and assumptions used;</P>
                <P>c. Ways to enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>d. Ways to minimize the burden of information collection on respondents, including through the use of automated collection techniques or other forms of information technology; and</P>
                <P>e. Estimates of capital or startup costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <P>At the end of the comment period, the comments and recommendations received will be analyzed to determine the extent to which the Board should modify the proposal.</P>
                <HD SOURCE="HD1">Proposal Under OMB Delegated Authority To Extend for Three Years, With Revision, the Following Information Collection</HD>
                <P>
                    <E T="03">Collection title:</E>
                     Ad Hoc Clearance for Board-Wide Use.
                </P>
                <P>
                    <E T="03">Collection identifier:</E>
                     FR 3100.
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0385.
                </P>
                <P>
                    <E T="03">General description of collection:</E>
                     Under this ad hoc clearance, information is collected from Board-regulated entities, other stakeholders, and the public (collectively, respondents) through to-be-defined surveys, interviews and focus groups, and other similar activities about a variety of financial service-related topics and the Board's operations. The clearance helps the Board understand respondents' perspectives, experiences, and expectations regarding the financial system and Board operations and could be used to inform the Board's initiatives to promote financial system stability, supervise and regulate financial institutions and financial activities, and promote consumer protection and community development.
                </P>
                <P>
                    <E T="03">Proposed revisions:</E>
                     Because there have been no uses of the FR 3100 since its initial clearance in 2023, the Board proposes to revise the FR 3100 by reducing the number of anticipated surveys by half from 20 to 10.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     As needed.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals, institutions, state and local governments, and other persons of interest to the Board.
                </P>
                <P>
                    <E T="03">Total estimated number of respondents:</E>
                     10.
                </P>
                <P>
                    <E T="03">Total estimated change in burden:</E>
                     (8,500).
                </P>
                <P>
                    <E T="03">Total estimated annual burden hours:</E>
                     8,500.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Erin M. Cayce,</NAME>
                    <TITLE>Assistant Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13858 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <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 received are subject to public disclosure. In general, comments received will be made available without change and will not be modified to remove personal or business information including confidential, contact, or other identifying information. Comments should not include any information such as confidential information that would not be appropriate for public disclosure.</P>
                <P>Comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors, Benjamin W. McDonough, Secretary of the Board, 20th Street and Constitution Avenue NW, Washington, DC 20551-0001, not later than August 10, 2026.</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">Nebraska Bankshares, Inc., Farnam, Nebraska, and its subsidiary, First Gothenburg Bancshares, Inc., Gothenburg, Nebraska;</E>
                     to acquire Foundations First Corporation, Omaha, Nebraska, and thereby indirectly acquire Foundation One Bank, Waterloo, Nebraska.
                </P>
                <SIG>
                    <PRTPAGE P="42446"/>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Michele Taylor Fennell,</NAME>
                    <TITLE>Associate Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13872 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE; P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Proposed Agency Information Collection Activities; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice, request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Board of Governors of the Federal Reserve System (Board) invites comment on a proposal to extend for three years, without revision, the Consumer and Stakeholder Surveys (FR 3073; OMB No. 7100-0359).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by FR 3073, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Agency Website: https://www.federalreserve.gov/apps/proposals/.</E>
                         Follow the instructions for submitting comments, including attachments. 
                        <E T="03">Preferred Method.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Benjamin W. McDonough, Secretary, Board of Governors of the Federal Reserve System, 20th Street and Constitution Avenue NW, Washington, DC 20551.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Same as mailing address.
                    </P>
                    <P>
                        • 
                        <E T="03">Other Means: publiccomments@frb.gov.</E>
                         You must include the OMB number or the FR number in the subject line of the message.
                    </P>
                    <P>
                        Comments received are subject to public disclosure. In general, comments received will be made available on the Board's website at 
                        <E T="03">https://www.federalreserve.gov/apps/proposals/</E>
                         without change and will not be modified to remove personal or business information including confidential, contact, or other identifying information. Comments should not include any information such as confidential information that would not be appropriate for public disclosure. Public comments may also be viewed electronically or in person in Room M-4365A, 2001 C St. NW, Washington, DC 20551, between 9 a.m. and 5 p.m. during Federal business weekdays.
                    </P>
                    <P>Additionally, commenters may send a copy of their comments to the Office of Management and Budget (OMB) Desk Officer for the Federal Reserve Board, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 10235, 725 17th Street NW, Washington, DC 20503, or by fax to (202) 395-6974.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Federal Reserve Board Clearance Officer—Nuha Elmaghrabi—Office of the Chief Data Officer, Board of Governors of the Federal Reserve System, 
                        <E T="03">nuha.elmaghrabi@frb.gov,</E>
                         (202) 452-3884.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On June 15, 1984, OMB delegated to the Board authority under the Paperwork Reduction Act (PRA) to approve and assign OMB control numbers to collections of information conducted or sponsored by the Board. In exercising this delegated authority, the Board is directed to take every reasonable step to solicit comment. In determining whether to approve a collection of information, the Board will consider all comments received from the public and other agencies.</P>
                <P>
                    During the comment period for this proposal, a copy of the proposed PRA OMB submission, including the draft reporting form and instructions, supporting statement (which contains more detail about the information collection and burden estimates than this notice), and other documentation, will be made available on the Board's public website at 
                    <E T="03">https://www.federalreserve.gov/apps/reportingforms/review</E>
                     or may be requested from the agency clearance officer, whose name appears above. On the page displayed at the link above, you can find the supporting information by referencing the collection identifier, FR 3073. Final versions of these documents will be made available at 
                    <E T="03">https://www.reginfo.gov/public/do/PRAMain,</E>
                     if approved.
                </P>
                <HD SOURCE="HD1">Request for Comment on Information Collection Proposal</HD>
                <P>The Board invites public comment on the following information collection, which is being reviewed under authority delegated by the OMB under the PRA. Comments are invited on the following:</P>
                <P>a. Whether the proposed collection of information is necessary for the proper performance of the Board's functions, including whether the information has practical utility;</P>
                <P>b. The accuracy of the Board's estimate of the burden of the proposed information collection, including the validity of the methodology and assumptions used;</P>
                <P>c. Ways to enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>d. Ways to minimize the burden of information collection on respondents, including through the use of automated collection techniques or other forms of information technology; and</P>
                <P>e. Estimates of capital or startup costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <P>At the end of the comment period, the comments and recommendations received will be analyzed to determine the extent to which the Board should modify the proposal.</P>
                <HD SOURCE="HD1">Proposal Under OMB Delegated Authority To Extend for Three Years, Without Revision, the Following Information Collection</HD>
                <P>
                    <E T="03">Collection title:</E>
                     Consumer and Stakeholder Surveys.
                </P>
                <P>
                    <E T="03">Collection identifier:</E>
                     FR 3073.
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0359.
                </P>
                <P>
                    <E T="03">General description of collection:</E>
                     The Board uses this collection to inform consumer-focused research, support its statutory responsibilities, and facilitate community development. The surveys in this collection inform the Board's work by identifying emerging risks and providing additional data on the issues that affect the well-being of consumers and communities and how the financial services marketplace functions.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Event-generated.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals and Board stakeholders, such as community groups, community development organizations, nonprofit service providers, faith-based service organizations, public sector agencies, small business owners, health care organizations, food banks, K-12 public and private schools, community colleges, community development financial institutions, credit unions, banks, and other financial institutions and companies offering financial products and services.
                </P>
                <P>
                    <E T="03">Total estimated number of respondents:</E>
                     Consumer surveys, 9,050; Stakeholder surveys 1,550.
                </P>
                <P>
                    <E T="03">Total estimated annual burden hours:</E>
                     12,380.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Erin M. Cayce,</NAME>
                    <TITLE>Assistant Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13906 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="42447"/>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Proposed Agency Information Collection Activities; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice, request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Board of Governors of the Federal Reserve System (Board) invites comment on a proposal to extend for three years, without revision, the Consumer Financial Protection Bureau's (CFPB) Regulation DD (CFPB DD; OMB No. 7100-0271).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by CFPB DD, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Agency Website: https://www.federalreserve.gov/apps/proposals/.</E>
                         Follow the instructions for submitting comments, including attachments. 
                        <E T="03">Preferred Method.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Benjamin W. McDonough, Secretary, Board of Governors of the Federal Reserve System, 20th Street and Constitution Avenue NW, Washington, DC 20551.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Same as mailing address.
                    </P>
                    <P>
                        • 
                        <E T="03">Other Means: publiccomments@frb.gov.</E>
                         You must include the OMB number or the collection identifier in the subject line of the message.
                    </P>
                    <P>
                        Comments received are subject to public disclosure. In general, comments received will be made available on the Board's website at 
                        <E T="03">https://www.federalreserve.gov/apps/proposals/</E>
                         without change and will not be modified to remove personal or business information including confidential, contact, or other identifying information. Comments should not include any information such as confidential information that would not be appropriate for public disclosure. Public comments may also be viewed electronically or in person in Room M-4365A, 2001 C St. NW, Washington, DC 20551, between 9 a.m. and 5 p.m. during Federal business weekdays.
                    </P>
                    <P>Additionally, commenters may send a copy of their comments to the Office of Management and Budget (OMB) Desk Officer for the Federal Reserve Board, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 10235, 725 17th Street NW, Washington, DC 20503, or by fax to (202) 395-6974.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Federal Reserve Board Clearance Officer—Nuha Elmaghrabi—Office of the Chief Data Officer, Board of Governors of the Federal Reserve System, 
                        <E T="03">nuha.elmaghrabi@frb.gov,</E>
                         (202) 452-3884.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On June 15, 1984, OMB delegated to the Board authority under the Paperwork Reduction Act (PRA) to approve and assign OMB control numbers to collections of information conducted or sponsored by the Board. In exercising this delegated authority, the Board is directed to take every reasonable step to solicit comment. In determining whether to approve a collection of information, the Board will consider all comments received from the public and other agencies.</P>
                <P>
                    During the comment period for this proposal, a copy of the proposed PRA OMB submission, including the draft reporting form and instructions, supporting statement (which contains more detail about the information collection and burden estimates than this notice), and other documentation, will be made available on the Board's public website at 
                    <E T="03">https://www.federalreserve.gov/apps/reportingforms/review</E>
                     or may be requested from the agency clearance officer, whose name appears above. On the page displayed at the link above, you can find the supporting information by referencing the collection identifier, CFPB DD. Final versions of these documents will be made available at 
                    <E T="03">https://www.reginfo.gov/public/do/PRAMain,</E>
                     if approved.
                </P>
                <HD SOURCE="HD1">Request for Comment on Information Collection Proposal</HD>
                <P>The Board invites public comment on the following information collection, which is being reviewed under authority delegated by the OMB under the PRA. Comments are invited on the following:</P>
                <P>a. Whether the proposed collection of information is necessary for the proper performance of the Board's functions, including whether the information has practical utility;</P>
                <P>b. The accuracy of the Board's estimate of the burden of the proposed information collection, including the validity of the methodology and assumptions used;</P>
                <P>c. Ways to enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>d. Ways to minimize the burden of information collection on respondents, including through the use of automated collection techniques or other forms of information technology; and</P>
                <P>e. Estimates of capital or startup costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <P>At the end of the comment period, the comments and recommendations received will be analyzed to determine the extent to which the Board should modify the proposal.</P>
                <HD SOURCE="HD1">Proposal Under OMB Delegated Authority To Extend for Three Years, Without Revision, the Following Information Collection</HD>
                <P>
                    <E T="03">Collection title:</E>
                     Disclosure Requirements Associated with the CFPB's Regulation DD.
                </P>
                <P>
                    <E T="03">Collection identifier:</E>
                     CFPB DD.
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0271.
                </P>
                <P>
                    <E T="03">General description of collection:</E>
                     The CFPB DD is the Board's information collection associated with the CFPB's Regulation DD, which implements the Truth in Savings Act to assist consumers in comparing deposit accounts offered by institutions, principally through the disclosure of fees, the annual percentage yield, and other account terms.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Event-generated.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     State member banks, branches of foreign banks (other than federal branches and insured state branches of foreign banks), commercial lending companies owned or controlled by foreign banks, and organizations operating under section 25 of the Federal Reserve Act (12 U.S.C. 601-604a).
                </P>
                <P>
                    <E T="03">Total estimated number of respondents:</E>
                     757.
                </P>
                <P>
                    <E T="03">Total estimated annual burden hours:</E>
                     24,981.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Erin M. Cayce,</NAME>
                    <TITLE>Assistant Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13859 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Proposed Agency Information Collection Activities; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice, request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Board of Governors of the Federal Reserve System (Board) invites comment on a proposal to extend for three years, with revision, the Domestic Finance Company Report of Consolidated Assets and Liabilities (FR 2248; OMB No. 7100-0005).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 8, 2026.</P>
                </DATES>
                <ADD>
                    <PRTPAGE P="42448"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by FR 2248, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Agency Website: https://www.federalreserve.gov/apps/proposals/.</E>
                         Follow the instructions for submitting comments, including attachments. 
                        <E T="03">Preferred Method.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Benjamin W. McDonough, Secretary, Board of Governors of the Federal Reserve System, 20th Street and Constitution Avenue NW, Washington, DC 20551.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Same as mailing address.
                    </P>
                    <P>
                        • 
                        <E T="03">Other Means: publiccomments@frb.gov.</E>
                         You must include the OMB number or the FR number in the subject line of the message.
                    </P>
                    <P>
                        Comments received are subject to public disclosure. In general, comments received will be made available on the Board's website at 
                        <E T="03">https://www.federalreserve.gov/apps/proposals/</E>
                         without change and will not be modified to remove personal or business information including confidential, contact, or other identifying information. Comments should not include any information such as confidential information that would not be appropriate for public disclosure. Public comments may also be viewed electronically or in person in Room M-4365A, 2001 C St. NW, Washington, DC 20551, between 9 a.m. and 5 p.m. during Federal business weekdays.
                    </P>
                    <P>Additionally, commenters may send a copy of their comments to the Office of Management and Budget (OMB) Desk Officer for the Federal Reserve Board, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 10235, 725 17th Street NW, Washington, DC 20503, or by fax to (202) 395-6974.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Federal Reserve Board Clearance Officer—Nuha Elmaghrabi—Office of the Chief Data Officer, Board of Governors of the Federal Reserve System, 
                        <E T="03">nuha.elmaghrabi@frb.gov,</E>
                         (202) 452-3884.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On June 15, 1984, OMB delegated to the Board authority under the Paperwork Reduction Act (PRA) to approve and assign OMB control numbers to collections of information conducted or sponsored by the Board. In exercising this delegated authority, the Board is directed to take every reasonable step to solicit comment. In determining whether to approve a collection of information, the Board will consider all comments received from the public and other agencies.</P>
                <P>
                    During the comment period for this proposal, a copy of the proposed PRA OMB submission, including the draft reporting form and instructions, supporting statement (which contains more detail about the information collection and burden estimates than this notice), and other documentation, will be made available on the Board's public website at 
                    <E T="03">https://www.federalreserve.gov/apps/reportingforms/review</E>
                     or may be requested from the agency clearance officer, whose name appears above. On the page displayed at the link above, you can find the supporting information by referencing the collection identifier, FR 2248. Final versions of these documents will be made available at 
                    <E T="03">https://www.reginfo.gov/public/do/PRAMain,</E>
                     if approved.
                </P>
                <HD SOURCE="HD1">Request for Comment on Information Collection Proposal</HD>
                <P>The Board invites public comment on the following information collection, which is being reviewed under authority delegated by the OMB under the PRA. Comments are invited on the following:</P>
                <P>a. Whether the proposed collection of information is necessary for the proper performance of the Board's functions, including whether the information has practical utility;</P>
                <P>b. The accuracy of the Board's estimate of the burden of the proposed information collection, including the validity of the methodology and assumptions used;</P>
                <P>c. Ways to enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>d. Ways to minimize the burden of information collection on respondents, including through the use of automated collection techniques or other forms of information technology; and</P>
                <P>e. Estimates of capital or startup costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <P>At the end of the comment period, the comments and recommendations received will be analyzed to determine the extent to which the Board should modify the proposal.</P>
                <HD SOURCE="HD1">Proposal Under OMB Delegated Authority To Extend for Three Years, With Revision, the Following Information Collection</HD>
                <P>
                    <E T="03">Collection title:</E>
                     Domestic Finance Company Report of Consolidated Assets and Liabilities.
                </P>
                <P>
                    <E T="03">Collection identifier:</E>
                     FR 2248.
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0005.
                </P>
                <P>
                    <E T="03">General description of collection:</E>
                     The voluntary FR 2248 is collected monthly as of the last calendar day of the month from a stratified sample of finance companies. Each monthly report collects balance sheet data on major categories of consumer and business credit receivables and on major short-term liabilities. For quarter-end months, additional asset and liability items are collected to provide a full balance sheet. Board staff may ask either quantitative or qualitative questions through the use of a special addendum section twice per year. The monthly and quarterly data are used to construct universe estimates of finance company holdings, which are published in the monthly statistical releases 
                    <E T="03">Consumer Credit</E>
                     (G.19) and 
                    <E T="03">Finance Companies</E>
                     (G.20), and in the quarterly statistical release 
                    <E T="03">Financial Accounts of the United States</E>
                     (Z.1).
                </P>
                <P>
                    <E T="03">Proposed revisions:</E>
                     The Board proposes to revise the FR 2248 to streamline the reporting form, reduce respondent burden, and improve clarity. The FR 2248 revisions, which would be effective for the June 2027 reporting period, include:
                </P>
                <P>
                    <E T="03">A. Removals:</E>
                </P>
                <P>• Removing the second column: off-balance-sheet securitization items. Following the broad adoption of the FAS 166/167 accounting standard in 2010, most off-balance sheet assets are reflected on book and thus the off-balance sheet items are no longer necessary;</P>
                <P>• Removing the first column header “on-balance-sheet” and “(Enter zero if none)”;</P>
                <P>• Removing three real estate loan items (3.a.1 through 3.a.3);</P>
                <P>• Removing both equity capital items, 8.a and 8.b.</P>
                <P>
                    <E T="03">B. Revisions:</E>
                </P>
                <P>• Revising line item descriptions for 3.f, 4.c, and 6 to delete “on-balance-sheet”;</P>
                <P>• Revising “Total Equity Capital” (8.c) to be renamed “Equity Capital” and renumbered from 8.c to 8;</P>
                <P>• Revising item 7.c to replace the term “Other” with “Non-recourse” in the phrase “Notes, Bonds, Debentures, and Other Debt”;</P>
                <P>• Revising item 7.d to replace “Parent Company” with “Affiliates” in the phrase “Debt Due to Parent Company”;</P>
                <P>• Revising line items 3, 3.d, 3.d.1, 3.d.2, and 3.f to replace the term “capital leases” with “finance leases”;</P>
                <P>• Revising “Net Loans and Capital Leases” (3) to delete “Net”;</P>
                <P>• Revising the instructions to reflect the proposed revisions to the reporting form.</P>
                <P>
                    <E T="03">C. Addition:</E>
                </P>
                <P>
                    • Adding one item for Real Estate Loans (3.a) as a result of the consolidation of real estate loan items 
                    <PRTPAGE P="42449"/>
                    3.a.1 through 3.a.3., which are being removed;
                </P>
                <P>• Adding a line item description for 7.c, “All other short- and long-term debt not elsewhere classified.”</P>
                <P>
                    <E T="03">Frequency:</E>
                     Monthly, quarterly, semiannually.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Finance companies.
                </P>
                <P>
                    <E T="03">Total estimated number of respondents:</E>
                     150.
                </P>
                <P>
                    <E T="03">Total estimated change in burden:</E>
                     (2,994).
                </P>
                <P>
                    <E T="03">Total estimated annual burden hours:</E>
                     4,605.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Erin M. Cayce,</NAME>
                    <TITLE>Assistant Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13857 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Agency Information Collection Activities: Announcement of Board Approval Under Delegated Authority and Submission to OMB</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Board of Governors of the Federal Reserve System (Board) is adopting a proposal to three years, with revision, the Census of Finance Companies and Other Lenders and Survey of Finance Companies (FR 3033p and FR 3033s; OMB No. 7100-0277).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The revisions are effective for the September 2026 survey.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Federal Reserve Board Clearance Officer—Nuha Elmaghrabi—Office of the Chief Data Officer, Board of Governors of the Federal Reserve System, 
                        <E T="03">nuha.elmaghrabi@frb.gov,</E>
                         (202) 452-3884.
                    </P>
                    <P>Office of Management and Budget (OMB) Desk Officer for the Federal Reserve Board, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 10235, 725 17th Street NW, Washington, DC 20503, or by fax to (202) 395-6974.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On June 15, 1984, OMB delegated to the Board authority under the Paperwork Reduction Act (PRA) to approve and assign OMB control numbers to collections of information conducted or sponsored by the Board. Board-approved collections of information are incorporated into the official OMB inventory of currently approved collections of information. The OMB inventory, as well as copies of the PRA Submission, supporting statements (which contain more detailed information about the information collections and burden estimates than this notice), and approved collection of information instrument(s) are available at 
                    <E T="03">https://www.reginfo.gov/public/do/PRAMain.</E>
                     These documents are also available on the Federal Reserve Board's public website at 
                    <E T="03">https://www.federalreserve.gov/apps/reportingforms/review</E>
                     or may be requested from the agency clearance officer, whose name appears above. On the page displayed at the link above, you can find the supporting information by referencing the collection identifier, FR 3033p and FR 3033s.
                </P>
                <HD SOURCE="HD1">Final Approval Under OMB Delegated Authority of the Extension for Three Years, With Revision, of the Following Information Collection</HD>
                <P>
                    <E T="03">Collection title:</E>
                     Census of Finance Companies and Other Lenders and Survey of Finance Companies.
                </P>
                <P>
                    <E T="03">Collection identifier:</E>
                     FR 3033p and FR 3033s.
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0277.
                </P>
                <P>
                    <E T="03">General description of collection:</E>
                     The FR 3033 information collection (the quinquennial) consists of the Census of Finance Companies and Other Lenders (FR 3033p), which the Board revised in May 2025, as well as the Survey of Finance Companies (FR 3033s), which the Board is revising at this time. The FR 3033p is the first part of a two-stage survey series, which has been conducted at a regular five-year interval since 1955. The second part of this information collection, the FR 3033s, collects balance sheet data on major categories of consumer and business credit receivables and major liabilities, along with income and expenses, and is used to gather information on the scope of the company's operations and loan and lease activities. In addition, questions were added to assess the current geographical penetration and online presence of finance companies. From the universe of finance companies determined by the FR 3033p, a stratified random sample of 3,000 finance companies will be drawn for the FR 3033s. This survey will be sent in May 2026 and will collect information as of December 31, 2025. The data collected from this voluntary survey will be used for two purposes: to benchmark the consumer and business finance series collected on the monthly Domestic Finance Company Report of Consolidated Assets and Liabilities (FR 2248; OMB No. 7100-0005) which in turn serves as an input to the following statistical releases: 
                    <E T="03">Finance Companies</E>
                     (G.20), 
                    <E T="03">Consumer Credit</E>
                     (G.19) and 
                    <E T="03">Financial Accounts of the United States</E>
                     (Z.1), and to increase the Federal Reserve's understanding of an important part of the financial system.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Quinquennially.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Finance companies.
                </P>
                <P>
                    <E T="03">Total estimated number of respondents:</E>
                     8,800.
                </P>
                <P>
                    <E T="03">Total estimated change in burden:</E>
                     (244).
                </P>
                <P>
                    <E T="03">Total estimated annual burden hours:</E>
                     3,512.
                </P>
                <P>
                    <E T="03">Current actions:</E>
                     On January 12, 2026, the Board published a notice in the 
                    <E T="04">Federal Register</E>
                     (91 FR 1186) requesting public comment for 60 days on the extension, with revision, of the FR 3033p and FR 3033s. The Board proposed to revise the FR 3033s to improve clarity, simplify the form overall, and collect additional information on the current geographical penetration and online presence of finance companies. The FR 3033p was not revised as part of this clearance. The comment period for this notice expired on March 13, 2026. The Board did not receive any comments. The revisions will be implemented as proposed.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System.</P>
                    <NAME>Erin M. Cayce,</NAME>
                    <TITLE>Assistant Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13904 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">GENERAL SERVICES ADMINISTRATION</AGENCY>
                <DEPDOC>[Notice-PBS-2026-01; Docket No. 2026-0002; Sequence No. 6]</DEPDOC>
                <SUBJECT>Notice of Intent To Prepare an Environmental Impact Statement for the Modernization and Expansion of the Nogales DeConcini Land Port of Entry in Nogales, Arizona</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Public Buildings Service (PBS), General Services Administration (GSA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Intent (NOI); announcement of public scoping meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Pursuant to the requirements of the National Environmental Policy Act of 1969 (NEPA) and the GSA Public Buildings Service NEPA Desk Guide, GSA is issuing this notice to advise the public that an Environmental Impact Statement (EIS) will be prepared to evaluate potential environmental impacts from the modernization and expansion of the Nogales DeConcini Land Port of Entry (LPOE) in Nogales, Arizona to address concerns related to the outdated and inefficient current LPOE layout and inadequate space and 
                        <PRTPAGE P="42450"/>
                        separation from the U.S.-Mexico border. This NOI also announces the public scoping process for the EIS.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Public Scoping Period</E>
                        —The public scoping period begins on Thursday, July 9, 2026. Interested parties are encouraged to provide comments regarding the scope of the EIS. Written comments must be received by Saturday, August 8, 2026 (see 
                        <E T="02">ADDRESSES</E>
                         section of this NOI on how to submit comments).
                    </P>
                    <P>
                        <E T="03">Meeting Date</E>
                        —A public scoping meeting will be held on Wednesday, July 22, 2026, from 4 p.m. to 6 p.m., Pacific Time (PT). The meeting will be held in the Nogales Recreation Center (see 
                        <E T="02">ADDRESSES</E>
                         section for location address), where GSA will meet with governmental and public stakeholders to explain the project and obtain input on the scope of the project.
                    </P>
                    <P>
                        <E T="03">The meeting will be an informal open house, where visitors may come, receive information, and provide written comments. No formal presentation will be provided.</E>
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">Public Scoping Comments</E>
                        —You may send comments, identified by [2026-0002], by one of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Email: Osmahn.Kadri@gsa.gov.</E>
                         Include [2026-0002] in the subject line of the message.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail: Attention:</E>
                         Osmahn Kadri, NEPA Project Manager, U.S. General Services Administration, c/o Potomac-Hudson Engineering, Inc., 77 Upper Rock Circle, Suite 302, Rockville MD 20850.
                    </P>
                    <P>
                        <E T="03">Meeting Location</E>
                        —The Nogales Recreation Center, 1500 Hohokam Dr., Nogales, AZ 85621.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Osmahn Kadri, 415-522-3617, 
                        <E T="03">Osmahn.Kadri@gsa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>The Nogales DeConcini LPOE is a multi-modal port, where Customs and Border Protection (CBP) currently inspects privately-owned vehicles (POVs), commercial buses (from 10 p.m. to 6 a.m.), and pedestrians at the U.S.-Mexico border in Nogales, Arizona. Pedestrians are currently processed 24 hours a day at the main Nogales DeConcini LPOE and from 10 a.m. to 6 p.m. at the adjacent Morley Gate pedestrian crossing. All commercial traffic, other than commercial buses from 10 p.m. to 6 a.m., is processed at the Nogales Mariposa LPOE that is just west of the Nogales DeConcini LPOE.</P>
                <P>The Nogales DeConcini LPOE is open 24 hours per day and has been operating since the 1930s. Construction of most of the current facility occurred during a facility renovation in the 1990s. The existing U.S. Custom House and Morley Gate were built in the 1930s and are both listed on the National Register of Historic Places.</P>
                <P>The current facilities at the Nogales DeConcini LPOE no longer function adequately given the site constraints, steady increase in traffic, and outdated facilities and technologies. The interaction between POVs, commercial buses, bus passengers, and pedestrian traffic is also a concern at the Nogales DeConcini LPOE. Inadequate pathways and separations between traffic types, along with persistent flooding and drainage issues, cause safety and security issues for CBP officers and the general public. As downtown Nogales is located just north and east of the Nogales DeConcini LPOE, traffic congestion and secure, efficient operation at the LPOE is also a concern in the community.</P>
                <P>To improve public and worker safety and to increase the capacity at the Nogales DeConcini LPOE, the proposed modernization and expansion would consist of replacement of all existing LPOE buildings, with the possible exception of the U.S. Custom House and Morley Gate, along with an expansion of the existing facility from five acres to up to approximately 25.5 acres. GSA intends to prepare an EIS to analyze the potential environmental impacts resulting from the proposed modernization and expansion of the Nogales DeConcini LPOE.</P>
                <P>Modernization and expansion of the existing Nogales DeConcini LPOE facilities would require a multi-phase construction plan to ensure that operations are continuous and that safety and security of the Nogales DeConcini LPOE is maintained.</P>
                <HD SOURCE="HD1">Alternatives Under Consideration</HD>
                <P>The EIS will consider two “action” alternatives and one “no action” alternative. Alternative 1 includes modernization and expansion of the LPOE in accordance with the program of requirements established in a 2025 Feasibility Study. This alternative includes consideration for multistory buildings including a parking garage with rooftop solar photovoltaic panels and potential reuse of the U.S. Custom House, along with eight outbound (to Mexico) POV/commercial bus lanes, 17 inbound (to U.S.) POV/commercial bus lanes, and approximately 16 pedestrian lanes at the main Nogales DeConcini LPOE. Morley Gate would remain with four pedestrian lanes, although lanes may be increased pending the results of an ongoing pedestrian origin and destination study. Alternative 1 would provide space to accommodate infrastructure for 5 additional inbound POV lanes that may be constructed at some point in the future. Consideration may also be given to moving bus passenger processing to Morley Gate. The pedestrian bridge from Morley Gate to the main port area would be reconstructed. Alternative 1 would provide the required 300 feet of separation from the border to allow for advanced security/processing technology and would allow designated SENTRI and Trusted Traveler lanes. Property acquisition of approximately four blocks to the north and west of the existing LPOE would be considered for the expansion. After construction, all commercial bus traffic would be directed to Nogales DeConcini LPOE due to the location of bus stations in downtown Nogales, AZ. Other commercial traffic would continue to utilize the Nogales Mariposa LPOE to the west. Alternative 2 includes construction of the LPOE similar to Alternative 1 but includes construction of 22 inbound (to the U.S.) POV/commercial bus lanes to account for potential long-term increases in latent demand and traffic. Facilities may also be slightly larger but the overall footprint of Alternative 2 would remain the same as Alternative 1. Construction and operations are expected to be similar to Alternative 1.</P>
                <P>The “no action” alternative assumes that GSA would not modernize or expand the Nogales DeConcini LPOE and that operations would continue under current conditions.</P>
                <P>The EIS will address the potential environmental impacts of the proposed alternatives on environmental resources including air quality during construction and operation, geology and soils, hazards and hazardous materials, water resources, hydrology and flooding, cultural resources, land use, noise during construction and operation, utilities, residential and commercial properties, and traffic. The EIS will also address the socioeconomic effects of the project on downtown Nogales. A pedestrian origin and destination study and a preliminary hydrologic and hydraulic analysis would also be conducted to help inform the EIS and eventual design of the facility.</P>
                <HD SOURCE="HD1">Scoping Process</HD>
                <P>
                    In accordance with 42 U.S.C. 4336a(c), the views and comments of the public are requested on alternatives or impacts and on relevant information, studies, or analyses with respect to the proposed agency action”. The scoping 
                    <PRTPAGE P="42451"/>
                    process will be accomplished through a public scoping meeting, and via direct mail correspondence to appropriate federal, state, and local agencies, and to private organizations and citizens who have previously expressed, or are known to have, an interest in the project.
                </P>
                <P>
                    A public scoping meeting will also be announced in the local newspaper, the 
                    <E T="03">Nogales International.</E>
                     Agencies and the public are encouraged to provide written comments regarding the scope of the EIS. See information provided above for dates, addresses, and contact information.
                </P>
                <P>
                    GSA will comply with Section 106 of the National Historic Preservation Act. Information received during the scoping period may be used to identify historic properties and parties interested in participating in the Section 106 process. Individuals and organizations with a demonstrated interest in the undertaking's effects on historic properties may request to participate as consulting parties by contacting Jason Hagin as 
                    <E T="03">jason.hagin@gsa.gov.</E>
                </P>
                <SIG>
                    <NAME>Osmahn Kadri,</NAME>
                    <TITLE>NEPA Program Manager, Office of Portfolio Management, Public Buildings Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13871 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6820-YF-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
                <DEPDOC>[CMS-3480-N]</DEPDOC>
                <SUBJECT>Secretarial Comments on the Consensus-Based Entity's (CBE) (Battelle Memorial Institute) 2025 Activities: Report to Congress and the Secretary of the Department of Health and Human Services</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary of Health and Human Services, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice acknowledges the Secretary of the Department of Health and Human Services' (the Secretary's) receipt and review of Battelle Memorial Institute's 2025 Annual Activities Report to Congress. The Battelle Memorial Institute is the consensus-based entity (CBE) under a contract with the Secretary, as mandated by section 1890(b)(5) of the Social Security Act (the Act). The Secretary has reviewed CBE's 2025 Annual Report and is publishing the report in the 
                        <E T="04">Federal Register</E>
                         together with the Secretary's comments on the report not later than 6 months after receiving the report in accordance with section 1890(b)(5)(B) of the Act. This notice fulfills the statutory requirements. The Act requires the Secretary to review and publish the report; however, this statutory obligation does not constitute endorsement by the Secretary of the CBE's annual report or its specific recommendations.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Charlayne Van, (410) 786-8659.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>The United States Department of Health and Human Services (HHS) has long recognized that a high functioning health care system that provides higher quality care requires accurate, valid, and reliable measurement of quality and efficiency. Section 183(a) of the Medicare Improvements for Patients and Providers Act of 2008 (MIPPA) (Pub. L. 110-275, July 15, 2008) added section 1890 of the Social Security Act (the Act), which requires the Secretary of HHS (the Secretary) to contract with a consensus-based entity (CBE) to perform multiple duties to help improve performance measurement. Section 3014 of the Patient Protection and Affordable Care Act (the Affordable Care Act) (Pub. L. 111-148, March 23, 2010) expanded the duties of the CBE to help in the identification of gaps in available measures and to improve the selection of measures used in health care programs in section 1890(b) of the Act. The below comments are regarding the 2025 activities conducted by Battelle as the CBE during that time.</P>
                <P>Section 1890(b) of the Act requires that the CBE synthesize evidence and convene key stakeholders to make recommendations on an integrated national strategy and priorities for health care performance measurement in all applicable settings. In doing so, pursuant to section 1890(b)(1)(A) of the Act, the CBE must give priority to measures that: (1) address the health care provided to patients with prevalent, high-cost chronic diseases; (2) have the greatest potential for improving quality, efficiency, and patient-centered health care; and (3) may be implemented rapidly due to existing evidence, standards of care, or other reasons. Additionally, pursuant to section 1890(b)(1)(B) of the Act, the CBE must take into account measures that: (1) may assist consumers and patients in making informed health care decisions; (2) address health disparities across groups and areas; and (3) address the continuum of care furnished by multiple providers or practitioners across multiple settings.</P>
                <P>
                    <E T="03">Endorsement of Measures.</E>
                     Under section 1890(b)(2)(A) through (B) of the Act, the CBE must provide for the endorsement of standardized health care performance measures. This process must consider whether measures are evidence-based, reliable, valid, verifiable, relevant to enhanced health outcomes, actionable at the caregiver level, feasible to collect and report, responsive to variations in patient characteristics such as health status, language capabilities, race or ethnicity, and income level and are consistent across types of health care providers, including hospitals and physicians.
                </P>
                <P>
                    <E T="03">Maintenance of CBE Endorsed Measures.</E>
                     The CBE is required to establish and implement a process to ensure that endorsed measures are updated (or retired if obsolete) as new evidence is developed.
                </P>
                <P>
                    <E T="03">Removal of Measures.</E>
                     Section 102(c) of Division CC of the Consolidated Appropriations Act, 2021 (Pub. L. 116-260, December 27, 2020) amended section 1890(b) of the Act to permit the CBE to provide input to the Secretary on measures that may be considered for removal.
                </P>
                <P>
                    <E T="03">Convening Multi-Stakeholder Groups.</E>
                     The CBE must convene multi-stakeholder groups to provide input on: (1) the selection of certain categories of quality and efficiency measures, from among such measures that have been endorsed by the entity and from among such measures that have not been considered for endorsement by such entity but are used or proposed to be used by the Secretary for the collection or reporting of quality and efficiency measures; and (2) national priorities for improvement in population health and in the delivery of health care services for consideration under the national strategy. The CBE provides input on measures for use in certain Medicare programs, for use in programs that report performance information to the public, and for use in health care programs that are not included under the Act. The multi-stakeholder groups provide input on quality and efficiency measures for various federal health care quality reporting and quality improvement programs including those that address certain Medicare services provided through hospices, ambulatory surgical centers, hospital inpatient and outpatient facilities, physician offices, cancer hospitals, end stage renal disease (ESRD) facilities, inpatient rehabilitation facilities, long-term care hospitals, psychiatric hospitals, and home health care programs.
                    <PRTPAGE P="42452"/>
                </P>
                <P>
                    <E T="03">Transmission of Multi-Stakeholder Input.</E>
                     Not later than February 1 of each year, the CBE must transmit to the Secretary the input of multi-stakeholder groups. Not later than March 1 of each year, the CBE is required to submit to the Congress and the Secretary an annual report. The report is to describe:
                </P>
                <P>• The implementation of quality and efficiency measurement initiatives and the coordination of such initiatives with quality and efficiency initiatives implemented by other payers;</P>
                <P>• Recommendations on an integrated national strategy and priorities for health care performance measurement;</P>
                <P>• Performance of the CBE's duties required under its contract with the Secretary;</P>
                <P>• Gaps in endorsed quality and efficiency measures, including measures that are within priority areas identified by the Secretary under the national strategy established under section 399HH of the Public Health Service Act (National Quality Strategy), and where quality and efficiency measures are unavailable or inadequate to identify or address such gaps;</P>
                <P>• Areas in which evidence is insufficient to support endorsement of quality and efficiency measures in priority areas identified by the Secretary under the National Quality Strategy, and where targeted research may address such gaps; and</P>
                <P>• The convening of multi-stakeholder groups to provide input on: (1) the selection of quality and efficiency measures from among such measures that have been endorsed by the CBE and such measures that have not been considered for endorsement by the CBE but are used or proposed to be used by the Secretary for the collection or reporting of quality and efficiency measures; and (2) national priorities for improvement in population health and the delivery of health care services for consideration under the National Quality Strategy.</P>
                <P>Section 50206(c)(1) of the Bipartisan Budget Act of 2018 (Pub. L. 115-123, February 9, 2018) amended section 1890(b)(5)(A) of the Act to require the CBE's annual report to Congress to include the following: (1) an itemization of financial information for the previous fiscal year ending September 30th, including annual revenues of the entity, annual expenses of the entity, and a breakdown of the amount awarded per contracted task order and the specific projects funded in each task order assigned to the entity; and (2) any updates or modifications to internal policies and procedures of the entity as they relate to the duties of the CBE including specifically identifying any modifications to the disclosure of interests and conflicts of interests for committees, work groups, task forces, and advisory panels of the entity, and information on external stakeholder participation in the duties of the entity.</P>
                <P>
                    The CBE must also annually provide a report to Congress and the Secretary under section 1890(b)(5)(A) of the Act. Section 1890(b)(5)(B) of the Act provides that no later than 6 months after receiving the annual report, the Secretary shall review such report; and publish such report in the 
                    <E T="04">Federal Register</E>
                    , together with any comments of the Secretary on such report.
                </P>
                <P>
                    This 
                    <E T="04">Federal Register</E>
                     notice satisfies the requirement for Secretarial review and publication of the CBE's annual report under section 1890(b)(5)(B) of the Act. The CBE submitted a report on its 2025 activities to Congress and the Secretary on February 24, 2026. The Secretary's Comments on this report are presented in section II. of this notice, and the CBE's 2025 Activities Report to Congress and the Secretary is provided, as submitted to HHS, in the addendum to this 
                    <E T="04">Federal Register</E>
                     notice in section IV.
                </P>
                <HD SOURCE="HD1">II. Secretarial Comments on the CBE's (Battelle Memorial Institute) 2025 Activities: Report to Congress and the Secretary of the Department of Health and Human Services</HD>
                <P>Pursuant to section 1890 of the Act, HHS is pleased to present the 2025 Annual Report from Battelle Memorial Institute, the designated CBE for health care quality measurement. This report details the significant progress made in advancing the quality, safety, and efficiency of America's healthcare system. We commend Battelle for their essential work in convening the Partnership for Quality Measurement, a broad coalition of patients, clinicians, payers, and other stakeholders, to provide transparent, evidence-informed recommendations on performance measures. This collaborative, consensus-driven process is fundamental to ensuring that quality measurement is both meaningful and scientifically robust, fostering trust and driving tangible improvements in care.</P>
                <P>The work detailed in this report directly supports key priorities of this Administration, particularly our commitment to promoting wellness and prevention and harnessing technology to build a more efficient and person-centered healthcare system. We are encouraged by the CBE's initiatives to integrate public health and preventive care measures, as highlighted by their focus on primary prevention and the establishment of a Wellness and Nutrition Framework. Furthermore, their forward-leaning efforts to advance the measurement landscape through technology are critical. The exploration of artificial intelligence to reduce provider burden and the development of a roadmap for digital quality measures are vital steps toward modernizing our health infrastructure, improving data accuracy, and ensuring that our quality programs keep pace with 21st-century care delivery.</P>
                <P>HHS values the contributions of the CBE and the hundreds of experts and patient representatives who volunteer their time to this consensus-building process. The insights and recommendations generated through this partnership are invaluable as we work to reduce unnecessary data collection burdens, align measures across federal programs, and focus on health outcomes that matter most to patients. We look forward to continuing this collaboration to advance a healthcare system that delivers better care, smarter spending, and healthier people.</P>
                <HD SOURCE="HD1">III. Collection of Information Requirements</HD>
                <P>
                    This document does not impose information collection requirements, that is, reporting, recordkeeping, or third-party disclosure requirements. Consequently, there is no need for review by the Office of Management and Budget under the authority of the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <HD SOURCE="HD1">IV. Addendum</HD>
                <P>
                    In this Addendum, we are publishing the 
                    <E T="03">CBE Report on 2025 Activities to Congress and the Secretary of the Department of Health and Human Services,</E>
                     as submitted to HHS.
                </P>
                <SIG>
                    <NAME>Robert F. Kennedy, Jr.,</NAME>
                    <TITLE>Secretary, Department of Health and Human Services.</TITLE>
                </SIG>
                <BILCOD>BILLING CODE 4169-69-P</BILCOD>
                <GPH SPAN="3" DEEP="564">
                    <PRTPAGE P="42453"/>
                    <GID>EN09JY26.000</GID>
                </GPH>
                <GPH SPAN="3" DEEP="584">
                    <PRTPAGE P="42454"/>
                    <GID>EN09JY26.001</GID>
                </GPH>
                <GPH SPAN="3" DEEP="584">
                    <PRTPAGE P="42455"/>
                    <GID>EN09JY26.002</GID>
                </GPH>
                <GPH SPAN="3" DEEP="584">
                    <PRTPAGE P="42456"/>
                    <GID>EN09JY26.003</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42457"/>
                    <GID>EN09JY26.004</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42458"/>
                    <GID>EN09JY26.005</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42459"/>
                    <GID>EN09JY26.006</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42460"/>
                    <GID>EN09JY26.007</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42461"/>
                    <GID>EN09JY26.008</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42462"/>
                    <GID>EN09JY26.009</GID>
                </GPH>
                <GPH SPAN="3" DEEP="565">
                    <PRTPAGE P="42463"/>
                    <GID>EN09JY26.010</GID>
                </GPH>
                <GPH SPAN="3" DEEP="569">
                    <PRTPAGE P="42464"/>
                    <GID>EN09JY26.011</GID>
                </GPH>
                <GPH SPAN="3" DEEP="568">
                    <PRTPAGE P="42465"/>
                    <GID>EN09JY26.012</GID>
                </GPH>
                <GPH SPAN="3" DEEP="569">
                    <PRTPAGE P="42466"/>
                    <GID>EN09JY26.013</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42467"/>
                    <GID>EN09JY26.014</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42468"/>
                    <GID>EN09JY26.015</GID>
                </GPH>
                <GPH SPAN="3" DEEP="584">
                    <PRTPAGE P="42469"/>
                    <GID>EN09JY26.016</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42470"/>
                    <GID>EN09JY26.017</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42471"/>
                    <GID>EN09JY26.018</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42472"/>
                    <GID>EN09JY26.019</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42473"/>
                    <GID>EN09JY26.020</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42474"/>
                    <GID>EN09JY26.021</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42475"/>
                    <GID>EN09JY26.022</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42476"/>
                    <GID>EN09JY26.023</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42477"/>
                    <GID>EN09JY26.024</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42478"/>
                    <GID>EN09JY26.025</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42479"/>
                    <GID>EN09JY26.026</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42480"/>
                    <GID>EN09JY26.027</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42481"/>
                    <GID>EN09JY26.028</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42482"/>
                    <GID>EN09JY26.029</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42483"/>
                    <GID>EN09JY26.030</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42484"/>
                    <GID>EN09JY26.031</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42485"/>
                    <GID>EN09JY26.032</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42486"/>
                    <GID>EN09JY26.033</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42487"/>
                    <GID>EN09JY26.034</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42488"/>
                    <GID>EN09JY26.035</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42489"/>
                    <GID>EN09JY26.036</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42490"/>
                    <GID>EN09JY26.037</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42491"/>
                    <GID>EN09JY26.038</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42492"/>
                    <GID>EN09JY26.039</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42493"/>
                    <GID>EN09JY26.040</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42494"/>
                    <GID>EN09JY26.041</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42495"/>
                    <GID>EN09JY26.042</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42496"/>
                    <GID>EN09JY26.043</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42497"/>
                    <GID>EN09JY26.044</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42498"/>
                    <GID>EN09JY26.045</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42499"/>
                    <GID>EN09JY26.046</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42500"/>
                    <GID>EN09JY26.047</GID>
                </GPH>
                <GPH SPAN="3" DEEP="569">
                    <PRTPAGE P="42501"/>
                    <GID>EN09JY26.048</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42502"/>
                    <GID>EN09JY26.049</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42503"/>
                    <GID>EN09JY26.050</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42504"/>
                    <GID>EN09JY26.051</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42505"/>
                    <GID>EN09JY26.052</GID>
                </GPH>
                <GPH SPAN="3" DEEP="570">
                    <PRTPAGE P="42506"/>
                    <GID>EN09JY26.053</GID>
                </GPH>
                <GPH SPAN="3" DEEP="569">
                    <PRTPAGE P="42507"/>
                    <GID>EN09JY26.054</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42508"/>
                    <GID>EN09JY26.055</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42509"/>
                    <GID>EN09JY26.056</GID>
                </GPH>
                <GPH SPAN="3" DEEP="593">
                    <PRTPAGE P="42510"/>
                    <GID>EN09JY26.057</GID>
                </GPH>
                <GPH SPAN="3" DEEP="569">
                    <PRTPAGE P="42511"/>
                    <GID>EN09JY26.058</GID>
                </GPH>
                <GPH SPAN="3" DEEP="569">
                    <PRTPAGE P="42512"/>
                    <GID>EN09JY26.059</GID>
                </GPH>
                <GPH SPAN="3" DEEP="569">
                    <PRTPAGE P="42513"/>
                    <GID>EN09JY26.060</GID>
                </GPH>
                <GPH SPAN="3" DEEP="569">
                    <PRTPAGE P="42514"/>
                    <GID>EN09JY26.061</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42515"/>
                    <GID>EN09JY26.062</GID>
                </GPH>
                <GPH SPAN="3" DEEP="569">
                    <PRTPAGE P="42516"/>
                    <GID>EN09JY26.063</GID>
                </GPH>
                <GPH SPAN="3" DEEP="584">
                    <PRTPAGE P="42517"/>
                    <GID>EN09JY26.064</GID>
                </GPH>
                <GPH SPAN="3" DEEP="584">
                    <PRTPAGE P="42518"/>
                    <GID>EN09JY26.065</GID>
                </GPH>
                <GPH SPAN="3" DEEP="584">
                    <PRTPAGE P="42519"/>
                    <GID>EN09JY26.066</GID>
                </GPH>
                <GPH SPAN="3" DEEP="584">
                    <PRTPAGE P="42520"/>
                    <GID>EN09JY26.067</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42521"/>
                    <GID>EN09JY26.068</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42522"/>
                    <GID>EN09JY26.069</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42523"/>
                    <GID>EN09JY26.070</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42524"/>
                    <GID>EN09JY26.071</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42525"/>
                    <GID>EN09JY26.072</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42526"/>
                    <GID>EN09JY26.073</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42527"/>
                    <GID>EN09JY26.074</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42528"/>
                    <GID>EN09JY26.075</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42529"/>
                    <GID>EN09JY26.076</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42530"/>
                    <GID>EN09JY26.077</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42531"/>
                    <GID>EN09JY26.078</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42532"/>
                    <GID>EN09JY26.079</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42533"/>
                    <GID>EN09JY26.080</GID>
                </GPH>
                <GPH SPAN="3" DEEP="571">
                    <PRTPAGE P="42534"/>
                    <GID>EN09JY26.081</GID>
                </GPH>
                <GPH SPAN="3" DEEP="584">
                    <PRTPAGE P="42535"/>
                    <GID>EN09JY26.082</GID>
                </GPH>
                <GPH SPAN="3" DEEP="572">
                    <PRTPAGE P="42536"/>
                    <GID>EN09JY26.083</GID>
                </GPH>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13865 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4169-69-C</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="42537"/>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. FDA-2026-P-1636]</DEPDOC>
                <SUBJECT>Determination That TOVALT ODT (Zolpidem Tartrate) Orally Disintegrating Tablets, 5 Milligrams and 10 Milligrams, 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, Agency, or we) has determined that TOVALT ODT (zolpidem tartrate) orally disintegrating tablets, 5 milligrams (mg) and 10 mg, were not withdrawn from sale for reasons of safety or effectiveness. This determination will allow FDA to approve abbreviated new drug applications (ANDAs) for zolpidem tartrate, orally disintegrating tablets, 5 mg and 10 mg, if all other legal and regulatory requirements are met.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Sungjoon Chi, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 51, Rm. 6216, Silver Spring, MD 20993-0002, 240-402-9674, 
                        <E T="03">sungjoon.chi@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>TOVALT ODT (zolpidem tartrate) orally disintegrating tablets, 5 mg and 10 mg, are the subject of NDA 021412, held by Biovail Laboratories International SRL, and initially approved on April 25, 2007. TOVALT ODT is indicated for the short-term treatment of insomnia characterized by difficulties with sleep initiation.</P>
                <P>
                    In a letter dated January 8, 2015, Valeant Pharmaceuticals North America, LLC, requested withdrawal of approval of NDA 021412 for TOVALT ODT (zolpidem tartrate) orally disintegrating tablets, 5 mg and 10 mg. In the 
                    <E T="04">Federal Register</E>
                     of June 21, 2017 (82 FR 28322), FDA announced that it was withdrawing approval of NDA 021412, effective July 21, 2017.
                </P>
                <P>LGM Pharma Solutions, LLC, submitted a citizen petition dated February 12, 2026 (Docket No. FDA-2026-P-1636), under 21 CFR 10.30, requesting that the Agency determine whether TOVALT ODT (zolpidem tartrate) orally disintegrating tablets, 5 mg and 10 mg, 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 TOVALT ODT (zolpidem tartrate) orally disintegrating tablets, 5 mg and 10 mg, were not withdrawn for reasons of safety or effectiveness. The petitioner has identified no data or other information suggesting that TOVALT ODT (zolpidem tartrate) orally disintegrating tablets, 5 mg and 10 mg, were withdrawn for reasons of safety or effectiveness. We have carefully reviewed our files for records concerning the withdrawal of TOVALT ODT (zolpidem tartrate) orally disintegrating tablets, 5 mg and 10 mg, from sale. We have also independently evaluated relevant literature and data for possible postmarketing adverse events. We have found no information that would indicate that this drug product was withdrawn from sale for reasons of safety or effectiveness.</P>
                <P>Accordingly, the Agency will continue to list TOVALT ODT (zolpidem tartrate) orally disintegrating tablets, 5 mg and 10 mg, 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. ANDAs that refer to these drug products may be approved by the Agency as long as they meet all other legal and regulatory requirements for the approval of ANDAs. If FDA determines that labeling for this drug product should be revised to meet current standards, the Agency will advise ANDA applicants to submit such labeling.</P>
                <SIG>
                    <NAME>Grace R. Graham,</NAME>
                    <TITLE>Deputy Commissioner for Policy, Legislation, and International Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13820 Filed 7-8-26; 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>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 1009 of the Federal Advisory Committee Act, as amended, notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Bioengineering and Instrumentation Development Review Panel.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 29, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 3:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Mir Ahamed Hossain, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 
                        <PRTPAGE P="42538"/>
                        20892, (301) 496-9223, 
                        <E T="03">mirahamed.hossain@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Contract Review: Mouse Models for Down Syndrome.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         August 3, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11:00 a.m. to 2:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate contract proposals.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Li Jia, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 451-2854, 
                        <E T="03">li.jia@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Contracts: NCI Research and Development.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         August 4, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate contract proposals.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         David G. Ransom, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, (RKL 2)/813-H, Bethesda, MD 20892 (301) 827-2574, 
                        <E T="03">ransomdg@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Program Projects: Lung and Sleep.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         August 4, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Melissa H. Nagelin, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892 (130) 159-4513, 
                        <E T="03">nagelinmh2@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Topics in HIV Comorbidities and Clinical Studies.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         August 4, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Melinda H. Krick, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Dr., Room 808G, Bethesda, MD 20892 (301) 435-1199, 
                        <E T="03">krickmh@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: HIV and Comorbidities Special Emphasis Panel.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         August 4, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 8:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Deanna C. Bublitz, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892 (301) 594-4005, 
                        <E T="03">deanna.bublitz@nih.gov</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; PAR Panel: Therapeutic Development for Neurological Disorders.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         August 5-6, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Kristin L. McNally, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 594-4079, 
                        <E T="03">mcnallyk@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Kidney, Urology, Reproduction and Skin.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         August 5, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Thomas John O'Farrell, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 594-3473, 
                        <E T="03">ofarrelltj@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Topics in Endocrinology and Metabolism.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         August 5, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Srihari Seshadri, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, (301) 594-4738, 
                        <E T="03">seshadris2@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Topics in Infectious Diseases.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         August 5, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         11:00 a.m. to 9:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Dayadevi Jirage, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4422, Bethesda, MD 20892, (301) 867-5309, 
                        <E T="03">jiragedb@csr.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine; 93.333, Clinical Research, 93.306, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Sterlyn H. Gibson, </NAME>
                    <TITLE>Program Specialist, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13864 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4167-05-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[Docket ID FEMA-2026-0002; Internal Agency Docket No. FEMA-B-2615]</DEPDOC>
                <SUBJECT>Proposed Flood Hazard Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Comments are requested on proposed flood hazard determinations, which may include additions or modifications of any Base Flood Elevation (BFE), base flood depth, Special Flood Hazard Area (SFHA) boundary or zone designation, or regulatory floodway on the Flood Insurance Rate Maps (FIRMs), and where applicable, in the supporting Flood Insurance Study (FIS) reports for the communities listed in the table below. The purpose of this notice is to seek general information and comment regarding the preliminary FIRM, and where applicable, the FIS report that the Federal Emergency Management Agency (FEMA) has provided to the affected communities. The FIRM and FIS report are the basis of the floodplain management measures that the community is required either to adopt or to show evidence of having in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments are to be submitted on or before October 7, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Preliminary FIRM, and where applicable, the FIS report for each community are available for inspection at both the online location 
                        <E T="03">https://hazards.fema.gov/femaportal/prelimdownload</E>
                         and the respective Community Map Repository address 
                        <PRTPAGE P="42539"/>
                        listed in the tables below. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                        <E T="03">https://msc.fema.gov</E>
                         for comparison.
                    </P>
                    <P>
                        You may submit comments, identified by Docket No. FEMA-B-2615, to David N. Bascom, Acting Director, Engineering and Modeling Division, Federal Insurance Directorate, Resilience, FEMA, 400 C Street SW, Washington, DC 20472, or (email) 
                        <E T="03">david.bascom@fema.dhs.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        David N. Bascom, Acting Director, Engineering and Modeling Division, Federal Insurance Directorate, Resilience, FEMA, 400 C Street SW, Washington, DC 20472, or (email) 
                        <E T="03">david.bascom@fema.dhs.gov;</E>
                         or visit the FEMA Mapping and Insurance eXchange (FMIX) online at 
                        <E T="03">https://www.floodmaps.fema.gov/fhm/fmx_main.html.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>FEMA proposes to make flood hazard determinations for each community listed below, in accordance with section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR 67.4(a).</P>
                <P>These proposed flood hazard determinations, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own or pursuant to policies established by other Federal, State, or regional entities. These flood hazard determinations are used to meet the floodplain management requirements of the NFIP.</P>
                <P>The communities affected by the flood hazard determinations are provided in the tables below. Any request for reconsideration of the revised flood hazard information shown on the Preliminary FIRM and FIS report that satisfies the data requirements outlined in 44 CFR 67.6(b) is considered an appeal. Comments unrelated to the flood hazard determinations also will be considered before the FIRM and FIS report become effective.</P>
                <P>
                    Use of a Scientific Resolution Panel (SRP) is available to communities in support of the appeal resolution process. SRPs are independent panels of experts in hydrology, hydraulics, and other pertinent sciences established to review conflicting scientific and technical data and provide recommendations for resolution. Use of the SRP only may be exercised after FEMA and local communities have been engaged in a collaborative consultation process for at least 60 days without a mutually acceptable resolution of an appeal. Additional information regarding the SRP process can be found online at 
                    <E T="03">https://www.floodsrp.org/pdfs/srp_overview.pdf.</E>
                </P>
                <P>
                    The watersheds and/or communities affected are listed in the tables below. The Preliminary FIRM, and where applicable, FIS report for each community are available for inspection at both the online location 
                    <E T="03">https://hazards.fema.gov/femaportal/prelimdownload</E>
                     and the respective Community Map Repository address listed in the tables. For communities with multiple ongoing Preliminary studies, the studies can be identified by the unique project number and Preliminary FIRM date listed in the tables. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                    <E T="03">https://msc.fema.gov</E>
                     for comparison.
                </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Elizabeth Asche,</NAME>
                    <TITLE>Assistant Administrator, Federal Insurance Directorate, Resilience Federal Emergency Management Agency, Department of Homeland Security.</TITLE>
                </SIG>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s100,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Community</CHED>
                        <CHED H="1">Community map repository address</CHED>
                    </BOXHD>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Fannin County, Georgia and Incorporated Areas</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Project: 19-04-0025S Preliminary Date: August 28, 2025</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="s">
                        <ENT I="01">Unincorporated Areas of Fannin County</ENT>
                        <ENT>Fannin County Courthouse, 400 West Main Street, Suite 101, Blue Ridge, GA 30513.</ENT>
                    </ROW>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Towns County, Georgia and Incorporated Areas</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Project: 19-04-0025S Preliminary Date: August 28, 2025</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">City of Hiawassee</ENT>
                        <ENT>City Hall, 50 River Street, Hiawassee, GA 30546.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">City of Young Harris</ENT>
                        <ENT>City Hall, 50 Irene Berry Drive, Young Harris, GA 30582.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Unincorporated Areas of Towns County</ENT>
                        <ENT>Towns County Courthouse, 48 River Street, Hiawassee, GA 30546.</ENT>
                    </ROW>
                    <ROW EXPSTB="01">
                        <ENT I="21">
                            <E T="02">Union County, Georgia and Incorporated Areas</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Project: 19-04-0025S Preliminary Date: August 28, 2025</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">City of Blairsville</ENT>
                        <ENT>City Hall, 62 Blue Ridge Street, Blairsville, GA 30512.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Unincorporated Areas of Union County</ENT>
                        <ENT>Union County Development Office, 46 Hughes Street, Suite A, Blairsville, GA 30512.</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13901 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="42540"/>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[Docket ID FEMA-2026-0002; Internal Agency Docket No. FEMA-B-2616]</DEPDOC>
                <SUBJECT>Changes in Flood Hazard Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice lists communities where the addition or modification of Base Flood Elevations (BFEs), base flood depths, Special Flood Hazard Area (SFHA) boundaries or zone designations, or the regulatory floodway (hereinafter referred to as flood hazard determinations), as shown on the Flood Insurance Rate Maps (FIRMs), and where applicable, in the supporting Flood Insurance Study (FIS) reports, prepared by the Federal Emergency Management Agency (FEMA) for each community, is appropriate because of new scientific or technical data. The FIRM, and where applicable, portions of the FIS report, have been revised to reflect these flood hazard determinations through issuance of a Letter of Map Revision (LOMR), in accordance with Federal Regulations. The current effective community number is shown in the table below and must be used for all new policies and renewals.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>These flood hazard determinations will be finalized on the dates listed in the table below and revise the FIRM panels and FIS report in effect prior to this determination for the listed communities.</P>
                    <P>From the date of the second publication of notification of these changes in a newspaper of local circulation, any person has 90 days in which to request through the community that the Assistant Administrator, Federal Insurance Directorate, Resilience reconsider the changes. The flood hazard determination information may be changed during the 90-day period.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The affected communities are listed in the table below. Revised flood hazard information for each community is available for inspection at both the online location and the respective community map repository address listed in the table below. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                        <E T="03">https://msc.fema.gov</E>
                         for comparison.
                    </P>
                    <P>Submit comments and/or appeals to the Chief Executive Officer of the community as listed in the table below.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        David N. Bascom, Acting Director, Engineering and Modeling Division, Federal Insurance Directorate, Resilience, FEMA, 400 C Street SW, Washington, DC 20472, or (email) 
                        <E T="03">david.bascom@fema.dhs.gov;</E>
                         or visit the FEMA Mapping and Insurance eXchange (FMIX) online at 
                        <E T="03">https://www.floodmaps.fema.gov/fhm/fmx_main.html.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The specific flood hazard determinations are not described for each community in this notice. However, the online location and local community map repository address where the flood hazard determination information is available for inspection is provided.</P>
                <P>Any request for reconsideration of flood hazard determinations must be submitted to the Chief Executive Officer of the community as listed in the table below.</P>
                <P>
                    The modifications are made pursuant to section 201 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4105, and are in accordance with the National Flood Insurance Act of 1968, 42 U.S.C. 4001 
                    <E T="03">et seq.,</E>
                     and with 44 CFR part 65.
                </P>
                <P>The FIRM and FIS report are the basis of the floodplain management measures that the community is required either to adopt or to show evidence of having in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
                <P>These flood hazard determinations, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own or pursuant to policies established by other Federal, State, or regional entities. The flood hazard determinations are in accordance with 44 CFR 65.4.</P>
                <P>
                    The affected communities are listed in the following table. Flood hazard determination information for each community is available for inspection at both the online location and the respective community map repository address listed in the table below. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                    <E T="03">https://msc.fema.gov</E>
                     for comparison.
                </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Elizabeth Asche,</NAME>
                    <TITLE>Assistant Administrator, Federal Insurance Directorate, Resilience, Federal Emergency Management Agency, Department of Homeland Security.</TITLE>
                </SIG>
                <GPOTABLE COLS="7" OPTS="L2,nj,tp0,p7,7/8,i1" CDEF="s50,xl50,xl75,xl75,xl90,xs55,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">State and county</CHED>
                        <CHED H="1">
                            Location and
                            <LI>case No.</LI>
                        </CHED>
                        <CHED H="1">
                            Chief executive officer
                            <LI>of community</LI>
                        </CHED>
                        <CHED H="1">
                            Community map
                            <LI>repository</LI>
                        </CHED>
                        <CHED H="1">
                            Online location of letter
                            <LI>of map revision</LI>
                        </CHED>
                        <CHED H="1">
                            Date of
                            <LI>modification</LI>
                        </CHED>
                        <CHED H="1">
                            Community
                            <LI>No.</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">Arizona:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa</ENT>
                        <ENT>City of Buckeye (26-09-0407X).</ENT>
                        <ENT>The Honorable Eric Orsborn, Mayor, City of Buckeye, 530 East Monroe Avenue, Buckeye, AZ 85326.</ENT>
                        <ENT>City Hall, 945 North 215th Avenue, Suite 137, Buckeye, AZ 85326.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 18, 2026</ENT>
                        <ENT>040039</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa</ENT>
                        <ENT>City of Chandler (24-09-0546P).</ENT>
                        <ENT>John Pombier, City Manager, City of Chandler, 175 South Arizona Avenue, Chandler, AZ 85225.</ENT>
                        <ENT>City Hall, 175 South Arizona Avenue, Chandler, AZ 85225.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>040040</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa</ENT>
                        <ENT>City of Glendale (25-09-0819P).</ENT>
                        <ENT>The Honorable Jerry P. Weiers, Mayor, City of Glendale, 5850 West Glendale Avenue, Glendale, AZ 85301.</ENT>
                        <ENT>Municipal Building, 5850 West Glendale Avenue, Glendale, AZ 85301.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 18, 2026</ENT>
                        <ENT>040045</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42541"/>
                        <ENT I="03">Maricopa</ENT>
                        <ENT>City of Goodyear (25-09-0819P).</ENT>
                        <ENT>The Honorable Joe Pizzillo, Mayor, City of Goodyear, 1900 North Civic Square, Goodyear, AZ 85395.</ENT>
                        <ENT>Development Services Department, 1900 North Civic Square, Goodyear, AZ 85395.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 18, 2026</ENT>
                        <ENT>040046</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa</ENT>
                        <ENT>City of Surprise (24-09-0192P).</ENT>
                        <ENT>The Honorable Kevin Sartor, Mayor, City of Surprise, 16000 North Civic Center Plaza, Surprise, AZ 85374.</ENT>
                        <ENT>City Hall, 16000 North Civic Center Plaza, Surprise, AZ 85374.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>040053</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa</ENT>
                        <ENT>Unincorporated Areas of Maricopa County (24-09-0192P).</ENT>
                        <ENT>Jennifer Pokorski, County Manager, Maricopa County, 301 West Jefferson Street, Phoenix, AZ 85003.</ENT>
                        <ENT>Flood Control District of Maricopa County, 2801 West Durango Street, Phoenix, AZ 85009.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>040037</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa</ENT>
                        <ENT>Unincorporated Areas of Maricopa County (25-09-0819P).</ENT>
                        <ENT>Jennifer Pokorski, County Manager, Maricopa County, 301 West Jefferson Street, Phoenix, AZ 85003.</ENT>
                        <ENT>Flood Control District of Maricopa County, 2801 West Durango Street, Phoenix, AZ 85009.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 18, 2026</ENT>
                        <ENT>040037</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa</ENT>
                        <ENT>Unincorporated Areas of Maricopa County (26-09-0406X).</ENT>
                        <ENT>Jennifer Pokorski, County Manager, Maricopa County, 301 West Jefferson Street, Phoenix, AZ 85003.</ENT>
                        <ENT>Flood Control District of Maricopa County, 2801 West Durango Street, Phoenix, AZ 85009.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 18, 2026</ENT>
                        <ENT>040037</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa</ENT>
                        <ENT>Unincorporated Areas of Maricopa County, 26-09-0407X).</ENT>
                        <ENT>Jennifer Pokorski, County Manager, Maricopa County, 301 West Jefferson Street, Phoenix, AZ 85003.</ENT>
                        <ENT>Flood Control District of Maricopa County, 2801 West Durango Street, Phoenix, AZ 85009.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 18, 2026</ENT>
                        <ENT>040037</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Pima</ENT>
                        <ENT>Town of Oro Valley (26-09-0352X).</ENT>
                        <ENT>The Honorable Joe Winfield, Mayor, Town of Oro Valley, 11000 North La Canada Drive, Oro Valley, AZ 85737.</ENT>
                        <ENT>Town Hall, 11000 North La Canada Drive, Oro Valley, AZ 85737.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 10, 2026</ENT>
                        <ENT>040109</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">California:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Riverside</ENT>
                        <ENT>City of Moreno Valley (26-09-0057P).</ENT>
                        <ENT>The Honorable Ulises Cabrera, Mayor, City of Moreno Valley, 14177 Frederick Street, Moreno Valley, CA 92552.</ENT>
                        <ENT>Public Works Department, 14177 Frederick Street, Moreno Valley, CA 92552.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 21, 2026</ENT>
                        <ENT>065074</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">San Diego</ENT>
                        <ENT>Unincorporated Areas of San Diego County (25-09-0691P).</ENT>
                        <ENT>Ebony N. Shelton, Chief Administrative Officer, San Diego County, 1600 Pacific Highway, Room 209, San Diego, CA 92101.</ENT>
                        <ENT>San Diego County, Planning and Development Services, 1600 Pacific Highway, San Diego, CA 92101.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 4, 2026</ENT>
                        <ENT>060284</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">San Mateo</ENT>
                        <ENT>City of Belmont (24-09-0381P).</ENT>
                        <ENT>The Honorable Julia Mates, Mayor, City of Belmont, 1 Twin Pines Lane, Belmont, CA 94002.</ENT>
                        <ENT>Public Works Department, 1 Twin Pines Lane, Belmont, CA 94002.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>065016</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">San Mateo</ENT>
                        <ENT>City of Foster City (24-09-0381P).</ENT>
                        <ENT>The Honorable Art Kiesel, Mayor, City of Foster City, 610 Foster City Boulevard, Foster City, CA 94404.</ENT>
                        <ENT>Public Works Department, 610 Foster City Boulevard, Foster City, CA 94404.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>060318</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">San Mateo</ENT>
                        <ENT>City of San Mateo (24-09-0381P).</ENT>
                        <ENT>The Honorable Adam Loraine, Mayor, City of San Mateo, 330 West 20th Avenue, San Mateo, CA 94403.</ENT>
                        <ENT>Public Works Department, 330 West 20th Avenue, San Mateo, CA 94403.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>060328</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Colorado:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Boulder</ENT>
                        <ENT>Unincorporated Areas of Boulder County (25-08-0638P).</ENT>
                        <ENT>The Honorable Claire Levy, Chair, Boulder County Board of Commissioners, P.O. Box 471, Boulder, CO 80306.</ENT>
                        <ENT>Boulder County Community, Planning and Permitting Building, 2045 13th Street, Boulder, CO 80302.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 3, 2026</ENT>
                        <ENT>080023</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Boulder</ENT>
                        <ENT>Unincorporated Areas of Boulder County (25-08-0713P).</ENT>
                        <ENT>The Honorable Claire Levy, Chair, Boulder County Board of Commissioners, P.O. Box 471, Boulder, CO 80306.</ENT>
                        <ENT>Boulder County Community, Planning and Permitting Building, 2045 13th Street, Boulder, CO 80302.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 21, 2026</ENT>
                        <ENT>080023</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Jefferson</ENT>
                        <ENT>City of Westminster (25-08-0416P).</ENT>
                        <ENT>The Honorable Claire Carmelia, Mayor, City of Westminster, 4800 West 92nd Avenue, Westminster, CO 80031.</ENT>
                        <ENT>City Hall, 4800 West 92nd Avenue, Westminster, CO 80031.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>080008</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42542"/>
                        <ENT I="03">Jefferson</ENT>
                        <ENT>Unincorporated Areas of Jefferson County (25-08-0416P).</ENT>
                        <ENT>The Honorable Lesley Dahlkemper, Chair, Jefferson County Board of Commissioners, 100 Jefferson County Parkway, Suite 5550, Golden, CO 80419.</ENT>
                        <ENT>Jefferson County, Planning and Zoning Division, 100 Jefferson County Parkway, Suite 3550, Golden, CO 80419.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>080087</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Larimer</ENT>
                        <ENT>Town of Wellington (24-08-0379P).</ENT>
                        <ENT>The Honorable Rebekka Dailey, Mayor, Town of Wellington, P.O. Box 127, Wellington, CO 80549.</ENT>
                        <ENT>Town Hall, 3735 Cleveland Street, Wellington, CO 80549.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 18, 2026</ENT>
                        <ENT>080104</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Larimer</ENT>
                        <ENT>Unincorporated Areas of Larimer County (24-08-0379P).</ENT>
                        <ENT>The Honorable Jody Shadduck-McNally, Chair, Larimer County Board of Commissioners, 200 West Oak Street, Suite 2200, Fort Collins, CO 80521.</ENT>
                        <ENT>Larimer County, Courthouse Offices Building, 200 West Oak Street, Suite 3000, Fort Collins, CO 80521.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 18, 2026</ENT>
                        <ENT>080101</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Larimer</ENT>
                        <ENT>Unincorporated Areas of Larimer County (25-08-0337P).</ENT>
                        <ENT>The Honorable Jody Shadduck-McNally, Chair, Larimer County Board of Commissioners, 200 West Oak Street, Suite 2200, Fort Collins, CO 80521.</ENT>
                        <ENT>Larimer County, Courthouse Offices Building, 200 West Oak Street, Suite 3000, Fort Collins, CO 80521.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 10, 2026</ENT>
                        <ENT>080101</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Larimer</ENT>
                        <ENT>Unincorporated Areas of Larimer County (25-08-0628P).</ENT>
                        <ENT>The Honorable Jody Shadduck-McNally, Chair, Larimer County Board of Commissioners, 200 West Oak Street, Suite 2200, Fort Collins, CO 80521.</ENT>
                        <ENT>Larimer County, Courthouse Offices Building, 200 West Oak Street, Suite 3000, Fort Collins, CO 80521.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 10, 2026</ENT>
                        <ENT>0 080101</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Pitkin</ENT>
                        <ENT>Unincorporated Areas of Pitkin County (25-08-0407P).</ENT>
                        <ENT>Kara Silbernagel, Interim County Manager, Pitkin County, 530 East Main Street, Aspen, CO 81611.</ENT>
                        <ENT>Pitkin County Administrative Building, 530 East Main Street, Suite 205, Aspen, CO 81611.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 4, 2026</ENT>
                        <ENT>080287</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Idaho: Kootenai</ENT>
                        <ENT>Unincorporated Areas of Kootenai County (25-10-0698P).</ENT>
                        <ENT>The Honorable Bruce Mattare, Kootenai County Board of County Commissioners, P.O. Box 9000, Coeur d'Alene, ID 83816.</ENT>
                        <ENT>Kootenai County Building, 451 North Government Way, Coeur d'Alene, ID 83814.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 16, 2026</ENT>
                        <ENT>160076</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Montana: Madison</ENT>
                        <ENT>Unincorporated Areas of Madison County (25-08-0693P).</ENT>
                        <ENT>Ronald E. Nye, Chair, Madison County Board of Commissioners, 111 East Wallace, Virginia City, MT 59755.</ENT>
                        <ENT>Madison County Planning Department, 7 Placer Loop, Virginia City, MT 59755.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 18, 2026</ENT>
                        <ENT>300043</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oregon: Jackson</ENT>
                        <ENT>Unincorporated Areas of Jackson County (26-10-0137X).</ENT>
                        <ENT>Danny Jordan, Jackson County Administrator, 10 South Oakdale Avenue, Room 214, Medford, OR 97501.</ENT>
                        <ENT>Jackson County Courthouse, 10 South Oakdale Avenue, Room 214, Medford, OR 97501.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 3, 2026</ENT>
                        <ENT>415589</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Washington:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">King</ENT>
                        <ENT>City of Seattle (25-10-0544P).</ENT>
                        <ENT>The Honorable Katie Wilson, Mayor, City of Seattle, P.O. Box 94749, Seattle, WA 98124.</ENT>
                        <ENT>City Hall, 600 4th Avenue, Seattle, WA 98104.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>530089</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">King</ENT>
                        <ENT>City of Tukwila (24-10-0399P).</ENT>
                        <ENT>The Honorable Thomas McLeod, Mayor, City of Tukwila, 6200 Southcenter Boulevard, Tukwila, WA 98188.</ENT>
                        <ENT>Public Works, 6300 Southcenter Boulevard, Suite 200, Tukwila, WA 98188.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>530091</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Kittitas</ENT>
                        <ENT>Unincorporated Areas of Kittitas County (24-10-0036P).</ENT>
                        <ENT>The Honorable Laura Osiadacz, Chair, Kittitas County Board of Commissioners, 205 West 5th Avenue, Suite 108, Ellensburg, WA 98926.</ENT>
                        <ENT>Kittitas County Department of Public Works, 411 North Ruby Street, Suite 1, Ellensburg, WA 98926.</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch.</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>530095</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13899 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="42543"/>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[Docket ID FEMA-2026-0002; Internal Agency Docket No. FEMA-B-2617]</DEPDOC>
                <SUBJECT>Changes in Flood Hazard Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice lists communities where the addition or modification of Base Flood Elevations (BFEs), base flood depths, Special Flood Hazard Area (SFHA) boundaries or zone designations, or the regulatory floodway (hereinafter referred to as flood hazard determinations), as shown on the Flood Insurance Rate Maps (FIRMs), and where applicable, in the supporting Flood Insurance Study (FIS) reports, prepared by the Federal Emergency Management Agency (FEMA) for each community, is appropriate because of new scientific or technical data. The FIRM, and where applicable, portions of the FIS report, have been revised to reflect these flood hazard determinations through issuance of a Letter of Map Revision (LOMR), in accordance with Federal Regulations. The current effective community number is shown in the table below and must be used for all new policies and renewals.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>These flood hazard determinations will be finalized on the dates listed in the table below and revise the FIRM panels and FIS report in effect prior to this determination for the listed communities.</P>
                    <P>From the date of the second publication of notification of these changes in a newspaper of local circulation, any person has 90 days in which to request through the community that the Assistant Administrator, Federal Insurance Directorate, Resilience reconsider the changes. The flood hazard determination information may be changed during the 90-day period.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The affected communities are listed in the table below. Revised flood hazard information for each community is available for inspection at both the online location and the respective community map repository address listed in the table below. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                        <E T="03">https://msc.fema.gov</E>
                         for comparison.
                    </P>
                    <P>Submit comments and/or appeals to the Chief Executive Officer of the community as listed in the table below.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        David N. Bascom, Acting Director, Engineering and Modeling Division, Federal Insurance Directorate, Resilience, FEMA, 400 C Street SW, Washington, DC 20472, or (email) 
                        <E T="03">david.bascom@fema.dhs.gov</E>
                        ; or visit the FEMA Mapping and Insurance eXchange (FMIX) online at 
                        <E T="03">https://www.floodmaps.fema.gov/fhm/fmx_main.html</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The specific flood hazard determinations are not described for each community in this notice. However, the online location and local community map repository address where the flood hazard determination information is available for inspection is provided.</P>
                <P>Any request for reconsideration of flood hazard determinations must be submitted to the Chief Executive Officer of the community as listed in the table below.</P>
                <P>
                    The modifications are made pursuant to section 201 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4105, and are in accordance with the National Flood Insurance Act of 1968, 42 U.S.C. 4001 
                    <E T="03">et seq.,</E>
                     and with 44 CFR part 65.
                </P>
                <P>The FIRM and FIS report are the basis of the floodplain management measures that the community is required either to adopt or to show evidence of having in effect in order to qualify or remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
                <P>These flood hazard determinations, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own or pursuant to policies established by other Federal, State, or regional entities. The flood hazard determinations are in accordance with 44 CFR 65.4.</P>
                <P>
                    The affected communities are listed in the following table. Flood hazard determination information for each community is available for inspection at both the online location and the respective community map repository address listed in the table below. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at 
                    <E T="03">https://msc.fema.gov</E>
                     for comparison.
                </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Elizabeth Asche,</NAME>
                    <TITLE>Assistant Administrator, Federal Insurance Directorate, Resilience Federal Emergency Management Agency, Department of Homeland Security.</TITLE>
                </SIG>
                <GPOTABLE COLS="07" OPTS="L2,nj,tp0,p7,7/8,i1" CDEF="s50,r50,r75,r75,r90,xs55,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">State and county</CHED>
                        <CHED H="1">
                            Location and
                            <LI>case No.</LI>
                        </CHED>
                        <CHED H="1">
                            Chief executive
                            <LI>officer of community</LI>
                        </CHED>
                        <CHED H="1">
                            Community map
                            <LI>repository</LI>
                        </CHED>
                        <CHED H="1">
                            Online location of
                            <LI>letter of map revision</LI>
                        </CHED>
                        <CHED H="1">
                            Date of
                            <LI>modification</LI>
                        </CHED>
                        <CHED H="1">
                            Community
                            <LI>No.</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">Florida: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Bay</ENT>
                        <ENT>City of Panama City (25-04-3979P)</ENT>
                        <ENT>Jonathan Hayes, City Manager, City of Panama City, 501 Harrison Avenue, Panama City, FL 32401</ENT>
                        <ENT>City Hall, 501 Harrison Avenue, Panama City, FL 32401</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 8, 2026</ENT>
                        <ENT>120012</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Bay</ENT>
                        <ENT>Unincorporated areas of Bay County (25-04-3979P)</ENT>
                        <ENT>Joel Schubert, Bay County Manager, 840 West 11th Street, Panama City, FL 32401</ENT>
                        <ENT>Bay County Planning and Zoning Department, 840 West 11th Street, Panama City, FL 32401</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 8, 2026</ENT>
                        <ENT>120004</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lake</ENT>
                        <ENT>City of Mount Dora (26-04-0112P)</ENT>
                        <ENT>The Honorable James Homich, Mayor, City of Mount Dora, 510 North Baker Street, Mount Dora, FL 32757</ENT>
                        <ENT>Building Department, 308 East 5th Avenue, Mount Dora, FL 32757</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>120137</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42544"/>
                        <ENT I="03">Lake</ENT>
                        <ENT>Unincorporated areas of Lake County (26-04-0112P)</ENT>
                        <ENT>The Honorable Leslie Campione, Chair, Lake County Board of Commissioners, 315 West Main Street, Tavares, FL 32778</ENT>
                        <ENT>Lake County Administration Building, 315 West Main Street, Tavares, FL 32778</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>120421</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lee</ENT>
                        <ENT>Town of Fort Myers Beach (26-04-0698P)</ENT>
                        <ENT>The Honorable Dan Allers, Mayor, Town of Fort Myers Beach, 2525 Estero Boulevard, Fort Myers Beach, FL 33931</ENT>
                        <ENT>Town Hall, 2525 Estero Boulevard, Fort Myers Beach, FL 33931</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 8, 2026</ENT>
                        <ENT>120673</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lee</ENT>
                        <ENT>Unincorporated areas of Lee County (26-04-0417P)</ENT>
                        <ENT>David Harner, Lee County Manager, 2115 2nd Street, Fort Myers, FL 33901</ENT>
                        <ENT>Lee County Building Department, 1500 Monroe Street, Fort Myers, FL 33901</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 8, 2026</ENT>
                        <ENT>125124</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lee</ENT>
                        <ENT>Unincorporated areas of Lee County (26-04-0574P)</ENT>
                        <ENT>David Harner, Lee County Manager, 2115 2nd Street, Fort Myers, FL 33901</ENT>
                        <ENT>Lee County Building Department, 1500 Monroe Street, Fort Myers, FL 33901</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 8, 2026</ENT>
                        <ENT>125124</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Manatee</ENT>
                        <ENT>Unincorporated areas of Manatee County (25-04-2180P)</ENT>
                        <ENT>Charlie Bishop, Manatee County Administrator, 9000 Town Center Parkway, Lakewood Ranch, FL 34202</ENT>
                        <ENT>Manatee County Administration Building, 9000 Town Center Parkway, Lakewood Ranch, FL 34202</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 3, 2026</ENT>
                        <ENT>120153</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Marion</ENT>
                        <ENT>City of Ocala (25-04-3947P)</ENT>
                        <ENT>Peter Lee, City Manager, City of Ocala, 110 Southeast Watula Avenue, Ocala, FL 34471</ENT>
                        <ENT>Stormwater Engineering Department, 1805 Northeast 30th Avenue, Building 300, Ocala, FL 34470</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 16, 2026</ENT>
                        <ENT>120330</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Marion</ENT>
                        <ENT>Unincorporated areas of Marion County (25-04-3947P)</ENT>
                        <ENT>Mounir Bouyounes, Marion County Administrator, 601 Southeast 25th Avenue, Ocala, FL 34471</ENT>
                        <ENT>Marion County Growth Services—Planning and Zoning, 2710 East Silver Springs Boulevard, Ocala, FL 34470</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 16, 2026</ENT>
                        <ENT>120160</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Monroe</ENT>
                        <ENT>Village of Islamorada (25-04-6910P)</ENT>
                        <ENT>The Honorable Sharon Mahoney, Mayor, Village of Islamorada, 86800 Overseas Highway, Islamorada, FL 33036</ENT>
                        <ENT>Building Department, 86800 Overseas Highways, Islamorada, FL 33036</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>120424</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Orange</ENT>
                        <ENT>Unincorporated areas of Orange County (25-04-6247P)</ENT>
                        <ENT>The Honorable Jerry L. Demings, Mayor, Orange County, 201 South Rosalind Avenue, 5th Floor, Orlando, FL 32801</ENT>
                        <ENT>Orange County Public Works Department, Stormwater Management Division, 4200 South John Young Parkway, Orlando, FL 32839</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 4, 2026</ENT>
                        <ENT>120179</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Orange</ENT>
                        <ENT>Unincorporated areas of Orange County (26-04-0112P)</ENT>
                        <ENT>The Honorable Jerry L. Demings, Mayor, Orange County, 201 South Rosalind Avenue, 5th Floor, Orlando, FL 32801</ENT>
                        <ENT>Orange County Public Works Department, Stormwater Management Division, 4200 South John Young Parkway, Orlando, FL 32839</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>120179</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Sarasota</ENT>
                        <ENT>Unincorporated areas of Sarasota County (25-04-6972P)</ENT>
                        <ENT>The Honorable Jonathan Lewis, Sarasota County Administrator, 1660 Ringling Boulevard, Sarasota, FL 34236</ENT>
                        <ENT>Sarasota County Government Center, 1001 Sarasota Center Boulevard, Sarasota, FL 34240</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 4, 2026</ENT>
                        <ENT>125144</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">St. Johns</ENT>
                        <ENT>Unincorporated areas of St. Johns County (25-04-1653P)</ENT>
                        <ENT>Joy Andrews, St. Johns County Administrator, 500 San Sebastian View, St. Augustine, FL 32084</ENT>
                        <ENT>St. Johns County Government, 500 San Sebastian View, St. Augustine, FL 32084</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 16, 2026</ENT>
                        <ENT>125147</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Massachusetts: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Barnstable</ENT>
                        <ENT>Town of Barnstable (25-01-1174P)</ENT>
                        <ENT>Mark S. Ells, Town Manager, Town of Barnstable, 367 Main Street, Hyannis, MA 02601</ENT>
                        <ENT>Inspectional Services Department, 200 Main Street, Hyannis, MA 02601</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>250001</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Middlesex</ENT>
                        <ENT>City of Lowell (26-01-0268P)</ENT>
                        <ENT>Thomas A. Golden, Jr., Manager, City of Lowell, 375 Merrimack Street, 2nd Floor, Room 43, Lowell, MA 01852</ENT>
                        <ENT>City Hall, 375 Merrimack Street, Lowell, MA 01852</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>250201</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Middlesex</ENT>
                        <ENT>Town of Chelmsford (26-01-0268P)</ENT>
                        <ENT>Paul Cohen, Manager, Town of Chelmsford, 50 Billerica Road, Chelmsford, MA 01824</ENT>
                        <ENT>Town Hall, 50 Billerica Road, Chelmsford, MA 01824</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>250188</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42545"/>
                        <ENT I="01">Michigan: Monroe</ENT>
                        <ENT>Charter Township of Berlin (24-05-1088P)</ENT>
                        <ENT>Mary Jo Gedelian, Township Supervisor, Charter Township of Berlin, 8000 Swan View Drive, Newport, MI 48166</ENT>
                        <ENT>Township Office, 8000 Swan View Drive, Newport, MI 48166</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 9, 2026</ENT>
                        <ENT>260143</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Nebraska: Lancaster</ENT>
                        <ENT>City of Lincoln (25-07-0389P)</ENT>
                        <ENT>The Honorable Leirion Gaylord Baird, Mayor, City of Lincoln, 555 South 10th Street, Lincoln, NE 68508</ENT>
                        <ENT>City Hall, 555 South 10th Street, Lincoln, NE 68508</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 16, 2026</ENT>
                        <ENT>315273</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">North Carolina:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Cabarrus</ENT>
                        <ENT>Town of Harrisburg (25-04-3420P)</ENT>
                        <ENT>The Honorable Jennifer Teague, Mayor, Town of Harrisburg, P.O. Box 100, Harrisburg, NC 28075</ENT>
                        <ENT>Town Hall, 400 Main Street, Suite 101, Harrisburg, NC 28075</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Jun. 26, 2026</ENT>
                        <ENT>370038</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Durham.</ENT>
                        <ENT>City of Durham (25-04-6256P)</ENT>
                        <ENT>The Honorable Leonardo Williams, Mayor, City of Durham, 101 City Hall Plaza, Durham, NC 27701</ENT>
                        <ENT>Durham City-County Planning Department, 101 City Hall Plaza, Durham, NC</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Jun. 22, 2026</ENT>
                        <ENT>370086</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Durham</ENT>
                        <ENT>Unincorporated areas of Durham County (25-04-6256P)</ENT>
                        <ENT>Mike Lee, Chair, Durham County Board of Commissioners, 200 East Main Street, Durham, NC 27701</ENT>
                        <ENT>Durham City-County Planning Department, 101 City Hall Plaza, Durham, NC 27701</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Jun. 22, 2026</ENT>
                        <ENT>370085</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Randolph</ENT>
                        <ENT>Unincorporated areas of Randolph County (25-04-6440P)</ENT>
                        <ENT>Darrell Frye, Chair, Randolph County Board of Commissioners, 725 McDowell Road, Asheboro, NC 27205</ENT>
                        <ENT>Randolph County Planning and Zoning, 204 East Academy Street, Asheboro, NC 27203</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Jun. 22, 2026</ENT>
                        <ENT>370195</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Wake</ENT>
                        <ENT>City of Raleigh (25-04-4809P)</ENT>
                        <ENT>The Honorable Janet Cowell, Mayor, City of Raleigh, P.O. Box 590, Raleigh, NC 27602</ENT>
                        <ENT>Planning and Development, 219 Fayetteville Street, Raleigh, NC 27601</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Jun. 29, 2026</ENT>
                        <ENT>370243</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Wake</ENT>
                        <ENT>Unincorporated areas of Wake County (25-04-4809P)</ENT>
                        <ENT>Susan Evans, Chair, Wake County Board of Commissioners, P.O. Box 550, Raleigh, NC 27602</ENT>
                        <ENT>Wake County Planning Department, 336 Fayetteville Street #500, Raleigh, NC 27601</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Jun. 29, 2026</ENT>
                        <ENT>370368</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pennsylvania: Allegheny</ENT>
                        <ENT>Township of Ross (25-03-0541P)</ENT>
                        <ENT>Jessica Crawshaw, Manager, Township of Ross, 1000 Ross Municipal Drive, Pittsburgh, PA 15237</ENT>
                        <ENT>Township Municipal Building, 1000 Ross Municipal Drive, Pittsburgh, PA 15237</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>420979</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">South Carolina: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Horry</ENT>
                        <ENT>City of Myrtle Beach (25-04-4447P)</ENT>
                        <ENT>Jonathan “Fox” Simons, Jr., City Manager, City of Myrtle Beach, P.O. Box 2468, Myrtle Beach, SC 29578</ENT>
                        <ENT>City Services Building, 921 North Oak Street, Myrtle Beach, SC 29577</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>450109</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Horry</ENT>
                        <ENT>Unincorporated areas of Horry County (25-04-4447P)</ENT>
                        <ENT>The Honorable Johnny Gardner, Chair, Horry County Council, P.O. Box 1236, Conway, SC 29528</ENT>
                        <ENT>Horry County Code Enforcement, 1301 2nd Avenue, Suite 1D09, Conway, SC 29526</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>450104</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lexington</ENT>
                        <ENT>Unincorporated areas of Lexington County (25-04-0629P)</ENT>
                        <ENT>The Honorable Darrell Hudson, Chair, Lexington County Council, 212 South Lake Drive, Lexington, SC 29072</ENT>
                        <ENT>Lexington County Administration Building, 212 South Lake Drive, Lexington, SC 29072</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>450129</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Richland</ENT>
                        <ENT>Town of Blythewood (26-04-0795P)</ENT>
                        <ENT>The Honorable Sloan J. Griffin III, Mayor, Town of Blythewood, P.O. Box 1004, Blythewood, SC 29016</ENT>
                        <ENT>Town Hall, 171 Langford Road, Blythewood, SC 29016</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>450258</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Richland</ENT>
                        <ENT>Unincorporated areas of Richland County (26-04-0795P)</ENT>
                        <ENT>The Honorable Jesica Mackey, Chair, Richland County Council, P.O. Box 192, Columbia, SC 29201</ENT>
                        <ENT>Richland County Administration Building, 2020 Hampton Street, Columbia, SC 29204</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>450170</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">York</ENT>
                        <ENT>Unincorporated areas of York County (25-04-5831P)</ENT>
                        <ENT>Joshua Edwards, York County Manager, P.O. Box 66, York, SC 29745</ENT>
                        <ENT>York County Planning and Development Services, 18 West Liberty Street, York, SC 29745</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 3, 2026</ENT>
                        <ENT>450193</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Tennessee: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Hamilton</ENT>
                        <ENT>City of Chattanooga (25-04-3371P)</ENT>
                        <ENT>The Honorable Tim Kelly, Mayor, City of Chattanooga, 101 East 11th Street, Chattanooga, TN 37402</ENT>
                        <ENT>Development Resource Center, Public Works—Land Development Office, 1250 Market Street, Suite 1000, Chattanooga, TN 37402</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Aug. 31, 2026</ENT>
                        <ENT>470072</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42546"/>
                        <ENT I="03">Hamilton</ENT>
                        <ENT>City of East Ridge (25-04-3371P)</ENT>
                        <ENT>The Honorable Brian Williams, Mayor, City of East Ridge, 1517 Tombras Avenue, East Ridge, TN 37412</ENT>
                        <ENT>City Hall, 1517 Tombras Avenue, East Ridge, TN 37412</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Aug. 31, 2026</ENT>
                        <ENT>475424</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Sevier</ENT>
                        <ENT>City of Pigeon Forge (25-04-5733P)</ENT>
                        <ENT>David Wear, City Manager, City of Pigeon Forge, P.O. Box 1350, Pigeon Forge, TN 37863</ENT>
                        <ENT>City Hall, 3221 Rena Street, Pigeon Forge, TN 37863</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 11, 2026</ENT>
                        <ENT>475442</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Texas: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Bell</ENT>
                        <ENT>City of Nolanville (25-06-2431P)</ENT>
                        <ENT>The Honorable Andy Williams, Mayor, City of Nolanville, 101 North 5th Street, Nolanville, TX 76559</ENT>
                        <ENT>City Hall, 101 North 5th Street, Nolanville, TX 76559</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 16, 2026</ENT>
                        <ENT>480032</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Bexar</ENT>
                        <ENT>City of San Antonio (26-06-0449P)</ENT>
                        <ENT>The Honorable Gina Ortiz Jones, Mayor, City of San Antonio, P.O. Box 839966, San Antonio, TX 78283</ENT>
                        <ENT>Public Works, Storm Water Division, 1901 South Alamo Street, 2nd Floor, San Antonio, TX 78204</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>480045</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Bexar</ENT>
                        <ENT>City of Schertz (25-06-2485P)</ENT>
                        <ENT>The Honorable Ralph Rodriguez, Mayor, City of Schertz, 1400 Schertz Parkway, Schertz, TX 78154</ENT>
                        <ENT>Public Works Department, 10 Commercial Place, Building 2, Schertz, TX 78154</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>480269</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Brazoria</ENT>
                        <ENT>City of Iowa Colony (24-06-2606P)</ENT>
                        <ENT>The Honorable Wil Kennedy, Mayor, City of Iowa Colony, 3144 Meridiana Parkway, Iowa Colony, TX 77583</ENT>
                        <ENT>City Hall, 3144 Meridiana Parkway, Iowa Colony, TX 77583</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 10, 2026</ENT>
                        <ENT>481071</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Brazoria</ENT>
                        <ENT>Unincorporated areas of Brazoria County (24-06-2606P)</ENT>
                        <ENT>The Honorable L.M. Sebesta, Jr., Brazoria County Judge, 111 East Locust Street, Angleton, TX 77515</ENT>
                        <ENT>Brazoria County West Annex Building, 451 North Velasco Street, Suite 210, Angleton, TX 77515</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 10, 2026</ENT>
                        <ENT>485458</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton</ENT>
                        <ENT>City of Aubrey (25-06-1657P)</ENT>
                        <ENT>The Honorable Chris Rich, Mayor, City of Aubrey, 107 South Main Street, Aubrey, TX 76227</ENT>
                        <ENT>City Hall, 107 South Main Street, Aubrey, TX 76227</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>480776</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton</ENT>
                        <ENT>Town of Prosper (25-06-2299P)</ENT>
                        <ENT>The Honorable David F. Bristol, Mayor, Town of Prosper, 250 West 1st Street, Prosper, TX 75078</ENT>
                        <ENT>Town Hall, 250 West 1st Street, Prosper, TX 75078</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>480141</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton</ENT>
                        <ENT>Unincorporated areas of Denton County (25-06-1657P)</ENT>
                        <ENT>The Honorable Andy Eads, Denton County Judge, 1 Courthouse Drive, Denton, TX 76208</ENT>
                        <ENT>Denton County Development Services, 3900 Morse Street, Denton, TX 76208</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>480774</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton</ENT>
                        <ENT>Unincorporated areas of Denton County (25-06-2299P)</ENT>
                        <ENT>The Honorable Andy Eads, Denton County Judge, 1 Courthouse Drive, Denton, TX 76208</ENT>
                        <ENT>Denton County Development Services, 3900 Morse Street, Denton, TX 76208</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>480774</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Kendall</ENT>
                        <ENT>Unincorporated areas of Kendall County (25-06-2438P)</ENT>
                        <ENT>The Honorable Shane Stolarczyk, Kendall County Judge, 201 East San Antonio Avenue, Suite 122, Boerne, TX 78006</ENT>
                        <ENT>Kendall County Courthouse, 400 East Blanco, Boerne, TX 78006</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>480417</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lubbock</ENT>
                        <ENT>City of Lubbock (23-06-2307P)</ENT>
                        <ENT>The Honorable Mark McBrayer, Mayor, City of Lubbock, P.O. Box 2000, Lubbock, TX 79457</ENT>
                        <ENT>City Hall, 1314 Avenue K, Lubbock, TX 79401</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 8, 2026</ENT>
                        <ENT>480452</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Real</ENT>
                        <ENT>Unincorporated areas of Real County (26-06-0463P)</ENT>
                        <ENT>The Honorable Bella A. Rubio, Real County Judge, P.O. Box 446, Leakey, TX 78873</ENT>
                        <ENT>Real County Courthouse, 146 Highway 83 South, Leakey, TX 78873</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 8, 2026</ENT>
                        <ENT>480978</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tarrant</ENT>
                        <ENT>City of Fort Worth (24-06-1155P)</ENT>
                        <ENT>The Honorable Mattie Parker, Mayor, City of Fort Worth, 100 Fort Worth Trail, Fort Worth, TX 76102</ENT>
                        <ENT>Department of Transportation and Public Works, Stormwater Management Division, 100 Fort Worth Trail, Fort Worth, TX 76102</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 3, 2026</ENT>
                        <ENT>480596</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Virginia:</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42547"/>
                        <ENT I="03">Goochland</ENT>
                        <ENT>Unincorporated areas of Goochland County (25-03-0514P)</ENT>
                        <ENT>Dr. Jeremy Raley, Goochland County Administrator, 1800 Sandy Hook Road, Goochland, VA 23063</ENT>
                        <ENT>Goochland County Administration Building, 1800 Sandy Hook Road, Suite 280, Goochland, VA 23063</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 3, 2026</ENT>
                        <ENT>510072</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Prince William</ENT>
                        <ENT>Unincorporated areas of Prince William County (26-03-0213X)</ENT>
                        <ENT>The Honorable Christopher Shorter, Prince William County Executive, 1 County Complex Court, Prince William, VA 22192</ENT>
                        <ENT>Prince William County Department of Public Works, Environmental Management Division, 5 County Complex Court, Suite 170, Prince William, VA 22192</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 4, 2026</ENT>
                        <ENT>510119</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wisconsin: Marathon</ENT>
                        <ENT>Village of Rib Mountain (26-05-0730P)</ENT>
                        <ENT>The Honorable Allen Opall, President, Village of Rib Mountain Board of Trustees, 227800 Snowbird Avenue, Rib Mountain, WI 54401</ENT>
                        <ENT>Municipal Center, 227800 Snowbird Avenue, Rib Mountain, WI 54401</ENT>
                        <ENT>
                            <E T="03">https://msc.fema.gov/portal/advanceSearch</E>
                        </ENT>
                        <ENT>Sep. 14, 2026</ENT>
                        <ENT>550642</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13900 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[Docket ID FEMA-2026-0002]</DEPDOC>
                <SUBJECT>Changes in Flood Hazard Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>New or modified Base (1-percent annual chance) Flood Elevations (BFEs), base flood depths, Special Flood Hazard Area (SFHA) boundaries or zone designations, and/or regulatory floodways (hereinafter referred to as flood hazard determinations) as shown on the indicated Letter of Map Revision (LOMR) for each of the communities listed in the table below are finalized. Each LOMR revises the Flood Insurance Rate Maps (FIRMs), and in some cases the Flood Insurance Study (FIS) reports, currently in effect for the listed communities.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Each LOMR was finalized as in the table below.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Each LOMR is available for inspection at both the respective Community Map Repository address listed in the table below and online through the FEMA Map Service Center at 
                        <E T="03">https://msc.fema.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        David N. Bascom, Acting Director, Engineering and Modeling Division, Federal Insurance Directorate, Resilience, FEMA, 400 C Street SW, Washington, DC 20472, or (email) 
                        <E T="03">david.bascom@fema.dhs.gov;</E>
                         or visit the FEMA Mapping and Insurance eXchange (FMIX) online at 
                        <E T="03">https://www.floodmaps.fema.gov/fhm/fmx_main.html.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Federal Emergency Management Agency (FEMA) makes the final flood hazard determinations as shown in the LOMRs for each community listed in the table below. Notice of these modified flood hazard determinations has been published in newspapers of local circulation and 90 days have elapsed since that publication. The Assistant Administrator, Federal Insurance Directorate, Resilience has resolved any appeals resulting from this notification.</P>
                <P>
                    The modified flood hazard determinations are made pursuant to section 206 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4105, and are in accordance with the National Flood Insurance Act of 1968, 42 U.S.C. 4001 
                    <E T="03">et seq.,</E>
                     and with 44 CFR part 65.
                </P>
                <P>The current effective community number is shown and must be used for all new policies and renewals.</P>
                <P>The new or modified flood hazard information is the basis for the floodplain management measures that the community is required either to adopt or to show evidence of being already in effect in order to remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
                <P>This new or modified flood hazard information, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own or pursuant to policies established by other Federal, State, or regional entities.</P>
                <P>This new or modified flood hazard determinations are used to meet the floodplain management requirements of the NFIP. The changes in flood hazard determinations are in accordance with 44 CFR 65.4.</P>
                <P>
                    Interested lessees and owners of real property are encouraged to review the final flood hazard information available at the address cited below for each community or online through the FEMA Map Service Center at 
                    <E T="03">https://msc.fema.gov.</E>
                </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Elizabeth Asche,</NAME>
                    <TITLE>Assistant Administrator, Federal Insurance Directorate, Resilience, Federal Emergency Management Agency, Department of Homeland Security.</TITLE>
                </SIG>
                <GPOTABLE COLS="6" OPTS="L2,nj,tp0,p7,7/8,i1" CDEF="s50,r50,r75,r75,xs55,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">State and county</CHED>
                        <CHED H="1">
                            Location and
                            <LI>case No.</LI>
                        </CHED>
                        <CHED H="1">
                            Chief executive officer
                            <LI>of community</LI>
                        </CHED>
                        <CHED H="1">
                            Community map
                            <LI>repository</LI>
                        </CHED>
                        <CHED H="1">
                            Date of
                            <LI>modification</LI>
                        </CHED>
                        <CHED H="1">Community No.</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">Arizona: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Graham (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Town of Thatcher (24-09-0863P)</ENT>
                        <ENT>The Honorable Jenny Howard, Mayor, Town of Thatcher, 3700 West Main Street, Thatcher, AZ 85552</ENT>
                        <ENT>Public Works Department, 3700 West Main Street, Thatcher, AZ 85552</ENT>
                        <ENT>Apr. 30, 2026</ENT>
                        <ENT>040117</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42548"/>
                        <ENT I="03">Graham (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Graham County (24-09-0863P)</ENT>
                        <ENT>The Honorable Clay Mack, Chair, Graham County Board of Supervisors, 921 West Thatcher Boulevard, Safford, AZ 85546</ENT>
                        <ENT>Graham County General Services Building, 921 West Thatcher Boulevard, Safford, AZ 85546</ENT>
                        <ENT>Apr. 30, 2026</ENT>
                        <ENT>040032</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Buckeye (25-09-0055P)</ENT>
                        <ENT>The Honorable Eric Orsborn, Mayor, City of Buckeye, 530 East Monroe Avenue, Buckeye, AZ 85326</ENT>
                        <ENT>City Hall, 945 North 215th Avenue, Suite 137, Buckeye, AZ 85326</ENT>
                        <ENT>Apr. 17, 2026</ENT>
                        <ENT>040039</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Buckeye (25-09-0372P)</ENT>
                        <ENT>The Honorable Eric Orsborn, Mayor, City of Buckeye, 530 East Monroe Avenue, Buckeye, AZ 85326</ENT>
                        <ENT>City Hall, 945 North 215th Avenue, Suite 137, Buckeye, AZ 85326</ENT>
                        <ENT>Apr. 20, 2026</ENT>
                        <ENT>040039</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Buckeye (25-09-0623P)</ENT>
                        <ENT>The Honorable Eric Orsborn, Mayor, City of Buckeye, 530 East Monroe Avenue, Buckeye, AZ 85326</ENT>
                        <ENT>City Hall, 945 North 215th Avenue, Suite 137, Buckeye, AZ 85236</ENT>
                        <ENT>Apr. 17, 2026</ENT>
                        <ENT>040039</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Chandler (25-09-0313P)</ENT>
                        <ENT>The Honorable Kevin Hartke, Mayor, City of Chandler, 175 South Arizona Avenue, Chandler, AZ 85225</ENT>
                        <ENT>City Hall, 175 South Arizona Avenue, Chandler, AZ 85225</ENT>
                        <ENT>Apr. 9, 2026</ENT>
                        <ENT>040040</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Glendale (25-09-0021P)</ENT>
                        <ENT>The Honorable Jerry P. Weiers, Mayor, City of Glendale, 9494 West Maryland Avenue, Glendale, AZ 85305</ENT>
                        <ENT>Municipal Building, 5850 West Glendale Avenue, Glendale, AZ 85301</ENT>
                        <ENT>Apr. 10, 2026</ENT>
                        <ENT>040045</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Phoenix (25-09-0641P)</ENT>
                        <ENT>The Honorable Kate Gallego, Mayor, City of Phoenix, 200 West Washington Street, 11th Floor, Phoenix, AZ 85003</ENT>
                        <ENT>City Hall, 200 West Washington Street, Phoenix, AZ 85003</ENT>
                        <ENT>Apr. 10, 2026</ENT>
                        <ENT>040051</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Scottsdale (25-09-0723P)</ENT>
                        <ENT>The Honorable Lisa Borowsky, Mayor, City of Scottsdale, 3939 North Drinkwater Boulevard, Scottsdale, AZ 85251</ENT>
                        <ENT>Stormwater and Floodplain Management, 7447 East Indian School Road, Scottsdale, AZ 85251</ENT>
                        <ENT>Apr. 30, 2026</ENT>
                        <ENT>045012</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Maricopa County (25-09-0021P)</ENT>
                        <ENT>Jennifer Pokorski, Maricopa County Manager, 301 West Jefferson Street, Phoenix, AZ 85003</ENT>
                        <ENT>Flood Control District of Maricopa County, 2801 West Durango Street, Phoenix, AZ 85009</ENT>
                        <ENT>Apr. 10, 2026</ENT>
                        <ENT>040037</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Maricopa County (25-09-0055P)</ENT>
                        <ENT>Jennifer Pokorski, Maricopa County Manager, 301 West Jefferson Street, Phoenix, AZ 85003</ENT>
                        <ENT>Flood Control District of Maricopa County, 2801 West Durango Street, Phoenix, AZ 85009</ENT>
                        <ENT>Apr. 17, 2026</ENT>
                        <ENT>040037</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Maricopa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Maricopa County (25-09-0623P)</ENT>
                        <ENT>Jennifer Pokorski, Maricopa County Manager, 301 West Jefferson Street, Phoenix, AZ 85003</ENT>
                        <ENT>Flood Control District of Maricopa County, 2801 West Durango Street, Phoenix, AZ 85009</ENT>
                        <ENT>Apr. 17, 2026</ENT>
                        <ENT>040037</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Pima (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Tucson (23-09-0429P)</ENT>
                        <ENT>The Honorable Regina Romero, Mayor, City of Tucson, 255 West Alameda Street, Tucson, AZ 85701</ENT>
                        <ENT>Planning and Development Services, 201 North Stone Avenue, 1st Floor, Tucson, AZ 85701</ENT>
                        <ENT>Apr. 13, 2026</ENT>
                        <ENT>040076</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Pima (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated Areas of Pima County (23-09-0429P)</ENT>
                        <ENT>Jan Lesher, County Administrator, Pima County, 115 North Church Avenue, Suite 231, Tucson, AZ 85701</ENT>
                        <ENT>Pima County Regional Flood Control District, 201 North Stone Avenue, 9th Floor, Tucson, AZ 85701</ENT>
                        <ENT>Apr. 13, 2026</ENT>
                        <ENT>040073</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Pinal (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Town of Florence (25-09-0443P)</ENT>
                        <ENT>The Honorable Keith Eaton, CBO, CFM, CFO, Mayor, Town of Florence, 775 North Main Street, Florence, AZ 85132</ENT>
                        <ENT>Town of Florence, 775 North Main Street, Florence, AZ 85132</ENT>
                        <ENT>Apr. 17, 2026</ENT>
                        <ENT>040084</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">California:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Alameda (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Livermore (24-09-0948P)</ENT>
                        <ENT>Marianna Burch, City Manager, City of Livermore, 1051 South Livermore Avenue, Livermore, CA 94550</ENT>
                        <ENT>City Hall, 1051 South Livermore Avenue, Livermore, CA 94550</ENT>
                        <ENT>Apr. 29, 2026</ENT>
                        <ENT>060008</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Alameda (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Pleasanton (24-09-0948P)</ENT>
                        <ENT>The Honorable Jack Balch, Mayor, City of Pleasanton, P.O. Box 520, Pleasanton, CA 94566</ENT>
                        <ENT>City Hall, 123 Main Street, Pleasanton, CA 94566</ENT>
                        <ENT>Apr. 29, 2026</ENT>
                        <ENT>060012</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Alameda (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Alameda County (24-09-0948P)</ENT>
                        <ENT>Susan S. Muranishi, Alameda County Administrator, 1221 Oak Street, Oakland, CA 94612</ENT>
                        <ENT>Alameda County Public Works Agency, 399 Elmhurst Street, Hayward, CA 94544</ENT>
                        <ENT>Apr. 29, 2026</ENT>
                        <ENT>060001</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Contra Costa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Concord (25-09-0389P)</ENT>
                        <ENT>The Honorable Carlyn Obringer, Mayor, City of Concord, 1950 Parkside Drive, Concord, CA 94519</ENT>
                        <ENT>City Hall, 1950 Parkside Drive, Concord, CA 94519</ENT>
                        <ENT>Apr. 22, 2026</ENT>
                        <ENT>065022</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Contra Costa (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Contra Costa County (25-09-0389P)</ENT>
                        <ENT>Monica Nino, Contra Costa County Administrator, 1025 Escobar Street, Martinez, CA 94553</ENT>
                        <ENT>Contra Costa County Public Works Department, 255 Glacier Drive, Martinez, CA 94553</ENT>
                        <ENT>Apr. 22, 2026</ENT>
                        <ENT>060025</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Fresno (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Fresno County (26-09-0081P)</ENT>
                        <ENT>Paul Nerland, Fresno County Administrative Officer, 2220 Tulare Street, 6th Floor, Fresno, CA 93721</ENT>
                        <ENT>Fresno County Clerk Office, 2220 Tulare Street, Fresno, CA 93721</ENT>
                        <ENT>Apr. 30, 2026</ENT>
                        <ENT>065029</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Orange (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Orange County (25-09-0245P)</ENT>
                        <ENT>Michelle Aguirre, CEO, Orange County, 400 West Civic Center Drive, Santa Ana, CA 92701</ENT>
                        <ENT>Orange County Public Works, 601 North Ross Street, Santa Ana, CA 92701</ENT>
                        <ENT>Apr. 6, 2026</ENT>
                        <ENT>060212</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Placer (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Lincoln (24-09-1115P)</ENT>
                        <ENT>The Honorable Holly Andreatta, Mayor, City of Lincoln, 600 6th Street, Lincoln, CA 95648</ENT>
                        <ENT>City Hall, 600 6th Street, Lincoln, CA 95648</ENT>
                        <ENT>Apr. 20, 2026</ENT>
                        <ENT>060241</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Placer (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Placer County, (24-09-1115P)</ENT>
                        <ENT>Daniel Chatigny, County Executive Officer, Placer County, 175 Fulweiler Avenue, Auburn, CA 95603</ENT>
                        <ENT>Placer County, Public Works Department, 3091 County Center Drive, Auburn, CA 95603</ENT>
                        <ENT>Apr. 20, 2026</ENT>
                        <ENT>060239</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42549"/>
                        <ENT I="03">Riverside (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Riverside County (24-09-0652P)</ENT>
                        <ENT>The Honorable V. Manuel Perez, Chair, Riverside County Board of Supervisors, 4080 Lemon Street, 5th Floor, Riverside, CA 92501</ENT>
                        <ENT>Riverside County Flood Control District Building, 1995 Market Street, Riverside, CA 92501</ENT>
                        <ENT>Apr. 23, 2026</ENT>
                        <ENT>060245</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">San Bernardino (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Colton (24-09-0652P)</ENT>
                        <ENT>The Honorable Frank J. Navarro, Mayor, City of Colton, 650 North La Cadena Drive, Colton, CA 92324</ENT>
                        <ENT>Corporate Yard, 160 South 10th Street, Colton, CA 92324</ENT>
                        <ENT>Apr. 23, 2026</ENT>
                        <ENT>060273</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tulare (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Farmersville (25-09-0374P)</ENT>
                        <ENT>The Honorable Tina Hernandez, Mayor, City of Farmersville, 909 West Visalia Road, Farmersville, CA 93223</ENT>
                        <ENT>City Hall, 909 West Visalia Road, Farmersville, CA 93223</ENT>
                        <ENT>Apr. 29, 2026</ENT>
                        <ENT>060405</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tulare (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Tulare County (25-09-0374P)</ENT>
                        <ENT>Jason T. Britt, County Administrative Officer, Tulare County, 2800 West Burrel Avenue, Visalia, CA 93291</ENT>
                        <ENT>Tulare County, Administration Building, 2800 West Burrel Avenue, Visalia, CA 93291</ENT>
                        <ENT>Apr. 29, 2026</ENT>
                        <ENT>065066</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Ventura (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Camarillo (25-09-0983P)</ENT>
                        <ENT>Greg Ramirez, City Manager, City of Camarillo, 601 Carmen Drive, Camarilla, CA 93010</ENT>
                        <ENT>City Hall, 601 Carmen Drive, Camarillo, CA 93010</ENT>
                        <ENT>Apr. 9, 2026</ENT>
                        <ENT>065020</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Ventura (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Thousand Oaks (25-09-0238P)</ENT>
                        <ENT>Andrew Powers, City Manager, City of Thousand Oaks, 2100 East Thousand Oaks Boulevard, Thousand Oaks, CA 91362</ENT>
                        <ENT>City Hall, 2100 East Thousand Oaks Boulevard, Thousand Oaks, CA 91362</ENT>
                        <ENT>Apr. 29, 2026</ENT>
                        <ENT>060422</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Ventura (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Ventura County (25-09-0983P)</ENT>
                        <ENT>The Honorable Janice S. Parvin, Chair, Board of Directors, Ventura County, 980 Enchanted Way, Suite 203, Simi Valley, CA 93065</ENT>
                        <ENT>Ventura County Government Center, 800 South Victoria Avenue, Ventura, CA 93009</ENT>
                        <ENT>Apr. 9, 2026</ENT>
                        <ENT>060413</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Colorado:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Adams (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Thornton (25-08-0358P)</ENT>
                        <ENT>The Honorable Jan Kulmann, Mayor, City of Thornton, 9500 Civic Center Drive, Thornton, CO 80229</ENT>
                        <ENT>City Hall, 9500 Civic Center Drive, Thornton, CO 80229</ENT>
                        <ENT>Apr. 10, 2026</ENT>
                        <ENT>080007</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Adams (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Adams County, (25-08-0358P)</ENT>
                        <ENT>The Honorable Lynn Baca, Chair, Adams County Board of Commissioners, 4430 South Adams County Parkway, Brighton, CO 80601</ENT>
                        <ENT>Adams County Community and Economic Development, 4430 South Adams County Parkway, 1st Floor, Suite W2000, Brighton, CO 80601</ENT>
                        <ENT>Apr. 10, 2026</ENT>
                        <ENT>080001</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Arapahoe (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Arapahoe County (25-08-0088P)</ENT>
                        <ENT>The Honorable Leslie Summey, Chair, Arapahoe County Board of Commissioners, 5334 South Prince Street, Littleton, CO 80120</ENT>
                        <ENT>Arapahoe County, Public Works and Development Department, 6924 South Lima Street, Centennial, CO 80112</ENT>
                        <ENT>Apr. 17, 2026</ENT>
                        <ENT>080011</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Boulder (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Boulder County (25-08-0480P)</ENT>
                        <ENT>The Honorable Marta Loachamin, Chair, Boulder County Board of Commissioners, Post Office Box 471, Boulder, CO 80306</ENT>
                        <ENT>Boulder County Community, Planning and Permitting Building, 2045 13th Street, Boulder, CO 80302</ENT>
                        <ENT>Apr. 13, 2026</ENT>
                        <ENT>080023</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denver (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City and County of Denver (25-08-0088P)</ENT>
                        <ENT>The Honorable Mike Johnston, Mayor, City and County of Denver, 1437 North Bannock Street, Room 350, Denver, CO 80202</ENT>
                        <ENT>City and County of Denver, Department of Public Works, 201 West Colfax Avenue, Denver, CO 80202</ENT>
                        <ENT>Apr. 17, 2026</ENT>
                        <ENT>080046</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Idaho:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Ada (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Eagle (25-10-0597P)</ENT>
                        <ENT>The Honorable Brad Pike, Mayor, City of Eagle, 660 East Civic Lane, Eagle, ID 83616</ENT>
                        <ENT>City Hall, 660 East Civic Lane, Eagle, ID 83616</ENT>
                        <ENT>Apr. 23, 2026</ENT>
                        <ENT>160003</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Ada (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Star (25-10-0597P)</ENT>
                        <ENT>The Honorable Trevor A. Chadwick, Mayor, City of Star, 10769 West State Street, Star, ID 83669</ENT>
                        <ENT>City Hall, 10769 West State Street, Star, ID 83669</ENT>
                        <ENT>Apr. 23, 2026</ENT>
                        <ENT>160236</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Ada (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Ada County (25-10-0597P)</ENT>
                        <ENT>The Honorable Rod Beck, Chair, Ada County Board of Commissioners, 200 West Front Street, Boise, ID 83702</ENT>
                        <ENT>Ada County Courthouse, 200 West Front Street, Boise, ID 83702</ENT>
                        <ENT>Apr. 23, 2026</ENT>
                        <ENT>160001</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Canyon (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Canyon County (24-10-0254P)</ENT>
                        <ENT>The Honorable Brad Holton, Chair, Canyon County Board of County Commissioners, 1115 Albany Street, Room 101, Caldwell, ID 83605</ENT>
                        <ENT>Canyon County Development Services Department, 111 North 11th Avenue, Room 310, Caldwell, ID 83605</ENT>
                        <ENT>Apr. 20, 2026</ENT>
                        <ENT>160208</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Nevada:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Clark (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Clark County (25-09-0382P)</ENT>
                        <ENT>The Honorable Tick Segerblom, Chair, Clark County Board of Commissioners, 500 South Grand Central Parkway, Las Vegas, NV 89155</ENT>
                        <ENT>Clark County Clerk's Office, 500 South Grand Central Parkway, Las Vegas, NV 89155</ENT>
                        <ENT>Apr. 14, 2026</ENT>
                        <ENT>320003</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lyon (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Fernley (25-09-0167P)</ENT>
                        <ENT>The Honorable Neal E. McIntyre, Mayor, City of Fernley, 595 Silver Lace Boulevard, Fernley, NV 89408</ENT>
                        <ENT>Public Works Department, 595 Silver Lace Boulevard, Fernley, NV 89408</ENT>
                        <ENT>Apr. 13, 2026</ENT>
                        <ENT>320038</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Oregon:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03"> Benton (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Benton County (25-10-0121P)</ENT>
                        <ENT>Rachel McEneny, Benton County Administrator, P.O. Box 3020, Corvallis, OR 97339</ENT>
                        <ENT>Benton County Community Development Department, 4500 Southwest Research Way, Corvallis, OR 97333</ENT>
                        <ENT>Apr. 29, 2026</ENT>
                        <ENT>410008</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Clackamas (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Happy Valley (25-10-0093P)</ENT>
                        <ENT>Jason Tuck, ICMA-CM, City Manager, City of Happy Valley, 1600 Southeast Misty Drive, Happy Valley, OR 97086</ENT>
                        <ENT>City Hall, 1600 Southeast Misty Drive, Happy Valley, OR 97086</ENT>
                        <ENT>Apr. 13, 2026</ENT>
                        <ENT>410026</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42550"/>
                        <ENT I="03">Washington (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Tualatin (25-10-0157P)</ENT>
                        <ENT>Sherilyn Lombos, City Manager, City of Tualatin, 18880 Southwest Martinazzi Avenue, Tualatin, OR 97062</ENT>
                        <ENT>City Offices, 18880 Southwest Martinazzi Avenue, Tualatin, OR 97062</ENT>
                        <ENT>April 15, 2026</ENT>
                        <ENT>410277</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">North Dakota: Cass (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Horace (25-08-0230P)</ENT>
                        <ENT>The Honorable Jeff Trudeau, Mayor, City of Horace, P.O. Box 99, Horace, ND 58047</ENT>
                        <ENT>City Hall, 215 Park Drive East, Horace, ND 58047</ENT>
                        <ENT>Apr. 13, 2026</ENT>
                        <ENT>380022</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">South Dakota:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lawrence (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Spearfish, (25-08-0037P)</ENT>
                        <ENT>The Honorable John Senden, Mayor, City of Spearfish, 625 North 5th Street, Spearfish, SD 57783</ENT>
                        <ENT>City Hall, 625 North 5th Street, Spearfish, SD 57783</ENT>
                        <ENT>Apr. 30, 2026</ENT>
                        <ENT>460046</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Meade (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Sturgis (25-08-0221P)</ENT>
                        <ENT>The Honorable Kevin Forrester, Mayor, City of Sturgis, 1040 Harley-Davidson Way, Sturgis, SD 57785</ENT>
                        <ENT>Administrative Building, 1040 Harley-Davidson Way, Sturgis, SD 57785</ENT>
                        <ENT>May 6, 2026</ENT>
                        <ENT>460055</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Utah:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Davis (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Layton (24-08-0321P)</ENT>
                        <ENT>The Honorable Joy Petro, Mayor, City of Layton, 437 North Wasatch Drive, Layton, UT 84041</ENT>
                        <ENT>Engineering Division, 437 North Wasatch Drive, Layton, UT 84041</ENT>
                        <ENT>Apr. 14, 2026</ENT>
                        <ENT>490047</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Weber (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Ogden (25-08-0165P)</ENT>
                        <ENT>The Honorable Benjamin K. Nadolski, Mayor, City of Ogden, 2549 Washington Boulevard, Ogden, UT 84401</ENT>
                        <ENT>City Hall, 2549 Washington Boulevard, Ogden, UT 84401</ENT>
                        <ENT>Apr. 10, 2026</ENT>
                        <ENT>490189</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Washington:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Clark (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>City of Washougal, (24-10-0232P)</ENT>
                        <ENT>David Scott, City Manager, City of Washougal, 1701 C Street, Washougal, WA 98671</ENT>
                        <ENT>City Hall, 1701 C Street, Washougal, WA 98671</ENT>
                        <ENT>Apr. 9, 2026</ENT>
                        <ENT>530028</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Clark (FEMA Docket, No.: B-2603)</ENT>
                        <ENT>Unincorporated areas of Clark County (24-10-0232P)</ENT>
                        <ENT>Kathleen Otto, County Manager, Clark County, P.O. Box 9810, Vancouver, WA 98666</ENT>
                        <ENT>Clark County, Public Service Center, 1300 Franklin Street, Vancouver, WA 98666</ENT>
                        <ENT>Apr. 9, 2026</ENT>
                        <ENT>530024</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13898 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[Docket ID FEMA-2026-0002]</DEPDOC>
                <SUBJECT>Changes in Flood Hazard Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>New or modified Base (1-percent annual chance) Flood Elevations (BFEs), base flood depths, Special Flood Hazard Area (SFHA) boundaries or zone designations, and/or regulatory floodways (hereinafter referred to as flood hazard determinations) as shown on the indicated Letter of Map Revision (LOMR) for each of the communities listed in the table below are finalized. Each LOMR revises the Flood Insurance Rate Maps (FIRMs), and in some cases the Flood Insurance Study (FIS) reports, currently in effect for the listed communities.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Each LOMR was finalized as in the table below.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Each LOMR is available for inspection at both the respective Community Map Repository address listed in the table below and online through the FEMA Map Service Center at 
                        <E T="03">https://msc.fema.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        David N. Bascom, Acting Director, Engineering and Modeling Division, National Flood Insurance Program, Resilience, FEMA, 400 C Street SW, Washington, DC 20472, or (email) 
                        <E T="03">david.bascom@fema.dhs.gov;</E>
                         or visit the FEMA Mapping and Insurance eXchange (FMIX) online at 
                        <E T="03">https://www.floodmaps.fema.gov/fhm/fmx_main.html.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Federal Emergency Management Agency (FEMA) makes the final flood hazard determinations as shown in the LOMRs for each community listed in the table below. Notice of these modified flood hazard determinations has been published in newspapers of local circulation and 90 days have elapsed since that publication. The Assistant Administrator, Federal Insurance Directorate, Resilience has resolved any appeals resulting from this notification.</P>
                <P>
                    The modified flood hazard determinations are made pursuant to section 206 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4105, and are in accordance with the National Flood Insurance Act of 1968, 42 U.S.C. 4001 
                    <E T="03">et seq.,</E>
                     and with 44 CFR part 65.
                </P>
                <P>The current effective community number is shown and must be used for all new policies and renewals.</P>
                <P>The new or modified flood hazard information is the basis for the floodplain management measures that the community is required either to adopt or to show evidence of being already in effect in order to remain qualified for participation in the National Flood Insurance Program (NFIP).</P>
                <P>This new or modified flood hazard information, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own or pursuant to policies established by other Federal, State, or regional entities.</P>
                <P>This new or modified flood hazard determinations are used to meet the floodplain management requirements of the NFIP. The changes in flood hazard determinations are in accordance with 44 CFR 65.4.</P>
                <P>
                    Interested lessees and owners of real property are encouraged to review the final flood hazard information available at the address cited below for each community or online through the FEMA Map Service Center at 
                    <E T="03">https://msc.fema.gov.</E>
                </P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance No. 97.022, “Flood Insurance.”)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Elizabeth Asche,</NAME>
                    <TITLE>Assistant Administrator, Federal Insurance Directorate, Resilience, Federal Emergency Management Agency, Department of Homeland Security.</TITLE>
                </SIG>
                <PRTPAGE P="42551"/>
                <GPOTABLE COLS="6" OPTS="L2,nj,tp0,p7,7/8,i1" CDEF="s50,xl50,xl90,xl90,xs60,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">State and county</CHED>
                        <CHED H="1">Location and case No.</CHED>
                        <CHED H="1">
                            Chief executive officer
                            <LI>of community</LI>
                        </CHED>
                        <CHED H="1">Community map repository</CHED>
                        <CHED H="1">
                            Date of
                            <LI>modification</LI>
                        </CHED>
                        <CHED H="1">
                            Community
                            <LI>No.</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Alabama: Madison (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Huntsville (25-04-3822P).</ENT>
                        <ENT>The Honorable Thomas Battle, Jr., Mayor, City of Huntsville, P.O. Box 308, Huntsville, AL 35804.</ENT>
                        <ENT>City Hall, P.O. Box 308, Huntsville, AL 35804.</ENT>
                        <ENT>Apr. 9, 2026</ENT>
                        <ENT>010153</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Florida:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Alachua (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Alachua County (25-04-4427P).</ENT>
                        <ENT>Michele Lieberman, County Manager, Alachua County, 12 Southeast 1st Street, Gainesville, FL 32601.</ENT>
                        <ENT>Public Works Department, 5620 Northwest 120th Lane, Gainesville, FL 32653.</ENT>
                        <ENT>Apr. 20, 2026</ENT>
                        <ENT>120001</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Brevard (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Palm Bay (25-04-3696P).</ENT>
                        <ENT>The Honorable Rob Medina, Mayor, City of Palm Bay, 120 Malabar Road Southeast, Palm Bay, FL 32907.</ENT>
                        <ENT>City Hall, 120 Malabar Road Southeast, Palm Bay, FL 32907.</ENT>
                        <ENT>Apr. 20, 2026</ENT>
                        <ENT>120404</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Clay (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Green Cove Springs (25-04-5404P).</ENT>
                        <ENT>Steve Kennedy, Manager, City of Green Cove Springs, 321 Walnut Street, Green Cove Springs, FL 32043.</ENT>
                        <ENT>City Hall, 321 Walnut Street, Green Cove Springs, FL 32043.</ENT>
                        <ENT>May. 1, 2026</ENT>
                        <ENT>120065</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lake (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Groveland (24-04-2030P).</ENT>
                        <ENT>Michael Hein, Manager, City of Groveland, 156 South Lake Avenue, Groveland, FL 34736.</ENT>
                        <ENT>City Hall, 156 South Lake Avenue, Groveland, FL 34736.</ENT>
                        <ENT>Apr. 21, 2026</ENT>
                        <ENT>120135</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lake (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Leesburg (25-04-4860P).</ENT>
                        <ENT>The Honorable Alan Reisman, Mayor, City of Leesburg, 501 West Meadow Street, Leesburg, FL 34748.</ENT>
                        <ENT>City Hall, 501 West Meadow Street, Leesburg, FL 34748.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>120136</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lake (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Lake County (24-04-2030P).</ENT>
                        <ENT>Jennifer Barker, Lake County Manager, 315 West Main Street, Tavares, FL 32778.</ENT>
                        <ENT>Lake County Public Works Department, 323 North Sinclair Avenue, Tavares, FL 32778.</ENT>
                        <ENT>Apr. 21, 2026</ENT>
                        <ENT>120421</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lee (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Cape Coral (25-04-1807P).</ENT>
                        <ENT>The Honorable John Gunter, Mayor, City of Cape Coral, 1015 Cultural Park Boulevard, Cape Coral, FL 33990.</ENT>
                        <ENT>City Hall, 1015 Cultural Park Boulevard, Cape Coral, FL 33990.</ENT>
                        <ENT>Apr. 21, 2026</ENT>
                        <ENT>125095</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Lee (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Lee County (25-04-1807P).</ENT>
                        <ENT>David Harner, Lee County Manager, 2115 2nd Street, Fort Myers, FL 33901.</ENT>
                        <ENT>Lee County Building Department, 1500 Monroe Street, Fort Myers, FL 33901.</ENT>
                        <ENT>Apr. 21, 2026</ENT>
                        <ENT>125124</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Monroe (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Monroe County (25-04-5374P).</ENT>
                        <ENT>The Honorable Michelle Lincoln, Mayor, Monroe County, Board of Commissioners, 530 Whitehead Street, Key West, FL 33040.</ENT>
                        <ENT>Monroe County Building Department, 2798 Overseas Highway, Suite 300, Marathon, FL 33050.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>125129</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Monroe (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Village of Islamorada (25-04-6836P).</ENT>
                        <ENT>The Honorable Sharon Mahoney, Mayor, Village of Islamorada, 86800 Overseas Highway, Islamorada, FL 33036.</ENT>
                        <ENT>Building Department, 86800 Overseas Highway, Islamorada, FL 33036.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>120424</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Osceola (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Osceola County (25-04-0716P).</ENT>
                        <ENT>Don Fisher, Manager, Osceola County, 1 Courthouse Square, Suite 4700, Kissimmee, FL 34741.</ENT>
                        <ENT>Osceola County Community Development Department, 1 Courthouse Square, Suite 1400, Kissimmee, FL 34741.</ENT>
                        <ENT>May. 1, 2026</ENT>
                        <ENT>120189</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Palm Beach (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Palm Beach County (25-04-1349P).</ENT>
                        <ENT>Joseph Abruzzo, Palm Beach County Administrator, 301 North Olive Avenue, West Palm Beach, FL 33401.</ENT>
                        <ENT>Palm Beach County Vista Center, Building Division Office, 2300 North Jog Road, West Palm Beach, FL 33411.</ENT>
                        <ENT>Apr. 20, 2026</ENT>
                        <ENT>120192</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Palm Beach (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Palm Beach County (25-04-2095P).</ENT>
                        <ENT>Joseph Abruzzo, Palm Beach County Administrator, 301 North Olive Avenue, West Palm Beach, FL 33401.</ENT>
                        <ENT>Palm Beach County Vista Center, Building Division Office, 2300 North Jog Road, West Palm Beach, FL 33411.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>120192</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Sarasota (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of North Port (25-04-3258P).</ENT>
                        <ENT>Jerome Fletcher, Manager, City of North Port, 4970 City Hall Boulevard, North Port, FL 34286.</ENT>
                        <ENT>City Hall, 4970 City Hall Boulevard, North Port, FL 34286.</ENT>
                        <ENT>May. 4, 2026</ENT>
                        <ENT>120279</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Georgia: Glynn (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Glynn County (24-04-2833P).</ENT>
                        <ENT>William Fallon, Manager, Glynn County, 1725 Reynolds Street, Suite 302, Brunswick, GA 31520.</ENT>
                        <ENT>Glynn County Clerk's Office, 1725 Reynolds Street, Suite 302, Brunswick, GA 31520.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>130092</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Kansas:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Johnson (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Mission Hills (25-07-0263P).</ENT>
                        <ENT>The Honorable David Dickey, Mayor, City of Mission Hills, 6300 State Line Road, Mission Hills, KS 66208.</ENT>
                        <ENT>City Hall, 6300 State Line Road, Mission Hills, KS 66208.</ENT>
                        <ENT>Apr. 28, 2026</ENT>
                        <ENT>200171</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Johnson (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Prairie Village (25-07-0263P).</ENT>
                        <ENT>The Honorable Eric Mikkelson, Mayor, City of Prairie Village, 7700 Mission Road, Prairie Village, KS 66208.</ENT>
                        <ENT>Public Works Department, 3535 Somerset Drive, Prairie Village, KS 66208.</ENT>
                        <ENT>Apr. 28, 2026</ENT>
                        <ENT>200175</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">North Carolina:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Brunswick (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Town of Leland (24-04-7093P).</ENT>
                        <ENT>The Honorable Brenda Bozeman, Mayor, Town of Leland, 102 Town Hall Drive, Leland, NC 28451.</ENT>
                        <ENT>Planning and Inspections, 102 Town Hall Drive, Leland, NC 28451.</ENT>
                        <ENT>Apr. 17, 2026</ENT>
                        <ENT>370471</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Brunswick (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Brunswick County (24-04-7093P).</ENT>
                        <ENT>Mike Forte, Chair, Brunswick County Board of Commissioners, P.O. Box 249, Bolivia, NC 28422.</ENT>
                        <ENT>Brunswick County Floodplain Management, 75 Courthouse Drive, Building I, Bolivia, NC 28422.</ENT>
                        <ENT>Apr. 17, 2026</ENT>
                        <ENT>370295</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Mecklenburg (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Charlotte (25-04-1331P).</ENT>
                        <ENT>The Honorable Vi Alexander Lyles, Mayor, City of Charlotte, 600 East 4th Street, Charlotte, NC 28202.</ENT>
                        <ENT>Mecklenburg County Stormwater Services Department, 2145 Suttle Avenue, Charlotte, NC 28208.</ENT>
                        <ENT>Apr. 2, 2026</ENT>
                        <ENT>370159</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Minnesota: Ramsey (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of New Brighton (24-05-0956P).</ENT>
                        <ENT>The Honorable Kari Niedfeldt-Thomas, Mayor, City of New Brighton, 803 Old Highway 8 Northwest, New Brighton, MN 55112.</ENT>
                        <ENT>City Hall, 803 Old Highway 8 Northwest, New Brighton, MN 55112.</ENT>
                        <ENT>Apr. 21, 2026</ENT>
                        <ENT>270380</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Nebraska: Lancaster (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Lincoln (25-07-0320P).</ENT>
                        <ENT>The Honorable Leirion Gaylor Baird, Mayor, City of Lincoln, 555 South 10th Street, Lincoln, NE 68508.</ENT>
                        <ENT>City Hall, 555 South 10th Street, Lincoln, NE 68508.</ENT>
                        <ENT>May. 4, 2026</ENT>
                        <ENT>315273</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42552"/>
                        <ENT I="01">New Jersey: Camden (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Borough of Gibbsboro (25-02-0385P).</ENT>
                        <ENT>The Honorable Edward G. Campbell, III, Mayor, Borough of Gibbsboro, 49 Kirkwood Road, Gibbsboro, NJ 08026.</ENT>
                        <ENT>Borough Hall, 49 Kirkwood Road, Gibbsboro, NJ 08026.</ENT>
                        <ENT>Apr. 23, 2026</ENT>
                        <ENT>340545</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New Mexico:, Bernalillo. (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Albuquerque (25-06-1638P).</ENT>
                        <ENT>The Honorable Tim Keller, Mayor, City of Albuquerque, P.O. Box 1293, Albuquerque NM 87103.</ENT>
                        <ENT>Albuquerque Government Center, 1 Civic Plaza, Albuquerque NM 87102.</ENT>
                        <ENT>Apr. 29, 2026</ENT>
                        <ENT>350002</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Oklahoma:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tulsa (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Broken Arrow (25-06-0409P).</ENT>
                        <ENT>Michael Spurgeon, Manager, City of Broken Arrow, 220 South 1st Street, Broken Arrow, OK 74012.</ENT>
                        <ENT>City Hall, 485 North Poplar Avenue, Broken Arrow, OK 74012.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>400236</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tulsa (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Tulsa (24-06-2324P).</ENT>
                        <ENT>The Honorable Monroe Nichols IV, Mayor, City of Tulsa, 175 East 2nd Street, Tulsa, OK 74103.</ENT>
                        <ENT>City Hall, 175 East 2nd Street, Suite 450, Tulsa, OK 74103.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>405381</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pennsylvania:, Bucks (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Borough of, Morrisville (25-03-0814P).</ENT>
                        <ENT>James J. Dillon, Interim Borough Manager, Borough of, Morrisville, 35 Union Street, Morrisville, PA 19067.</ENT>
                        <ENT>Borough Hall, 35 Union Street, Morrisville, PA 19067.</ENT>
                        <ENT>Apr. 23, 2026</ENT>
                        <ENT>420194</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Texas:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Bastrop (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Elgin (24-06-2254P).</ENT>
                        <ENT>Isaac Turner, Interim City Manager, City of Elgin, P.O. Box 591, Elgin, TX 78621.</ENT>
                        <ENT>City Hall, 310 North Main Street, Elgin, TX 78621.</ENT>
                        <ENT>Apr. 23, 2026</ENT>
                        <ENT>480023</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Bastrop (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Bastrop County (24-06-2254P).</ENT>
                        <ENT>The Honorable Gregory Klaus, Bastrop County Judge, 804 Pecan Street, Bastrop, TX 78602.</ENT>
                        <ENT>Bastrop County Floodplain Management, 211 Jackson Street, Bastrop, TX 78602.</ENT>
                        <ENT>Apr. 23, 2026</ENT>
                        <ENT>481193</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Collin (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Celina (25-06-1111P).</ENT>
                        <ENT>The Honorable Ryan Tubbs, Mayor, City of Celina, 142 North Ohio Street, Celina, TX 75009.</ENT>
                        <ENT>City Hall, 142 North Ohio Street, Celina, TX 75009.</ENT>
                        <ENT>Apr. 20, 2026</ENT>
                        <ENT>480133</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Collin (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Celina (25-06-1321P).</ENT>
                        <ENT>The Honorable Ryan Tubbs, Mayor, City of Celina, 142 North Ohio Street, Celina, TX 75009.</ENT>
                        <ENT>City Hall, 142 North Ohio Street, Celina, TX 75009.</ENT>
                        <ENT>May 4, 2026</ENT>
                        <ENT>480133</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Collin (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Celina (25-06-2559P).</ENT>
                        <ENT>The Honorable Ryan Tubbs, Mayor, City of Celina, 142 North Ohio Street, Celina, TX 75009.</ENT>
                        <ENT>City Hall, 142 North Ohio Street, Celina, TX 75009.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>480133</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Collin (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Frisco (25-06-1569P).</ENT>
                        <ENT>The Honorable Jeff Cheney, Mayor, City of Frisco, 6101 Frisco Square Boulevard, Frisco, TX 75034.</ENT>
                        <ENT>Engineering Development Department, 6101 Frisco Square Boulevard, Frisco, TX 75034.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>480134</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Collin (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Collin County (25-06-1321P).</ENT>
                        <ENT>The Honorable Chris Hill, Collin County Judge, 2300 Bloomdale Road, 1st Floor, McKinney, TX 75071.</ENT>
                        <ENT>Collin County Engineering Building, 4690 Community Avenue, Suite 200, McKinney, TX 75071.</ENT>
                        <ENT>May 4, 2026</ENT>
                        <ENT>480130</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Celina (25-06-1900P).</ENT>
                        <ENT>The Honorable Ryan Tubbs, Mayor, City of Celina, 142 North Ohio Street, Celina, TX 75009.</ENT>
                        <ENT>City Hall, 142 North Ohio Street, Celina, TX 75009.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>480133</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Fort Worth (25-06-0622P).</ENT>
                        <ENT>The Honorable Mattie Parker, Mayor, City of Fort Worth, 100 Fort Worth Trail, Fort Worth, TX 76102.</ENT>
                        <ENT>City Hall, 100 Fort Worth Trail, Fort Worth, TX 76102.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>480596</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Denton County (25-06-0622P).</ENT>
                        <ENT>The Honorable Andy Eads, Denton County Judge, 1 Courthouse Drive, Denton, TX 76208.</ENT>
                        <ENT>Denton County Development Services, 3900 Morse Street, Denton, TX 76208.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>480774</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Denton (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Denton County (25-06-1900P).</ENT>
                        <ENT>The Honorable Andy Eads, Denton County Judge, 1 Courthouse Drive, Denton, TX 76208.</ENT>
                        <ENT>Denton County Development Services, 3900 Morse Street, Denton, TX 76208.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>480774</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Guadalupe (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Cibolo (25-06-0322P).</ENT>
                        <ENT>The Honorable Mark Allen, Mayor, City of Cibolo, 200 South Main Street, Cibolo, TX 78108.</ENT>
                        <ENT>Public Works Department, 108 Cibolo Drive, Cibolo, TX 78108.</ENT>
                        <ENT>Apr. 27, 2026</ENT>
                        <ENT>480267</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Rockwall (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Rockwall (25-06-0733P).</ENT>
                        <ENT>The Honorable Tim McCallum, Mayor, City of Rockwall, 385 South Goliad Street, Rockwall, TX 75087.</ENT>
                        <ENT>City Hall, 385 South Goliad Street, Rockwall, TX 75087.</ENT>
                        <ENT>Apr. 24, 2026</ENT>
                        <ENT>480547</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Tarrant (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Fort Worth (25-06-2323P).</ENT>
                        <ENT>The Honorable Mattie Parker, Mayor, City of Fort Worth, 100 Fort Worth Trail, Fort Worth, TX 76102.</ENT>
                        <ENT>Department of Transportation and Public Works, 100 Fort Worth Trail, Fort Worth, TX 76102.</ENT>
                        <ENT>Apr. 20, 2026</ENT>
                        <ENT>480596</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Wisconsin:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Kenosha (FEMA Docket No.: B-2605)</ENT>
                        <ENT>City of Kenosha (25-05-2231X).</ENT>
                        <ENT>The Honorable David Bogdala, Mayor, City of Kenosha, 625 52nd Street, Room 300, Kenosha, WI 53140.</ENT>
                        <ENT>City Hall, 625 52nd Street, Room 308, Kenosha, WI 53140.</ENT>
                        <ENT>Apr. 22, 2026</ENT>
                        <ENT>550209</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Kenosha (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Kenosha County (25-05-2231X).</ENT>
                        <ENT>The Honorable Samantha Kerkman, Kenosha County Executive, 1010 56th Street, Kenosha, WI 53140.</ENT>
                        <ENT>Kenosha County Center, 19600 75th Street, Suite 185-3, Bristol, WI 53104.</ENT>
                        <ENT>Apr. 22, 2026</ENT>
                        <ENT>550523</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Outagamie (FEMA Docket No.: B-2605)</ENT>
                        <ENT>Unincorporated areas of Outagamie County (24-05-2691P).</ENT>
                        <ENT>The Honorable Thomas M. Nelson, Executive, Outagamie County, 320 South Walnut Street, Appleton, WI 54911.</ENT>
                        <ENT>Outagamie County Government Center, 320 South Walnut Street, Appleton, WI 54911.</ENT>
                        <ENT>Apr. 21, 2026</ENT>
                        <ENT>550302</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13897 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-12-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="42553"/>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-6568-N-04]</DEPDOC>
                <SUBJECT>Notice of HUD-Held Healthcare Loan Sale (HLS 2026-2)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Housing—Federal Housing Commissioner, U.S. Department of Housing and Urban Development (HUD).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of sale of 14 healthcare mortgage loans secured by 13 properties.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>HUD is announcing the competitive, sealed bid sale of 14 unsubsidized healthcare mortgage loans, without Federal Housing Administration (FHA) insurance. This sale, referred to as HLS 2026-2, is scheduled to occur on or about August 11, 2026. The sale supports HUD's efforts to maximize recoveries and reduce the cost of holding defaulted assets. This notice also describes generally the bidding process for the sale and certain persons who are ineligible to bid.  </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>
                        <E T="03">Bidder's Information Package (BIP) Available:</E>
                         On or about July 15, 2026.
                    </P>
                    <P>
                        <E T="03">Bid Date:</E>
                         On or about August 11, 2026 (bids must be submitted during specified hours).
                    </P>
                    <P>
                        <E T="03">Anticipated Award Date:</E>
                         On or before August 14, 2026.
                    </P>
                    <P>
                        <E T="03">Closing Date:</E>
                         On or about September 1, 2026.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Prospective bidders must complete, sign, and submit a Confidentiality Agreement and a Qualification Statement that meet HUD's requirements. These documents will be accessible via Mission Capital Advisors' bidding platform at 
                        <E T="03">market.missioncap.com,</E>
                         where participants can also register and submit all required documentation electronically. Questions about the bidder qualification process may be sent to: Transaction Specialist at 1-844-709-0763 or email 
                        <E T="03">HUDSales@FalconAssetSales.com.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        John Lucey, Director, Office of Asset Sales, U.S. Department of Housing and Urban Development, 451 7th St. SW, Washington, DC 20410; telephone 202-402-3927 (this is not a toll-free number), or at 
                        <E T="03">John.W.Lucey@hud.gov.</E>
                         HUD welcomes and is prepared to receive calls from individuals who are deaf or hard of hearing, as well as individuals with speech or communication disabilities. To learn more about how to make an accessible telephone call, please visit 
                        <E T="03">https://www.fcc.gov/consumers/guides/telecommunications-relay-service-trs.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>HUD is announcing its intention to sell 14 unsubsidized, non-performing healthcare mortgage loans (the “Mortgage Loans”) in Loan Sale HLS 2026-2. The Mortgage Loans will be sold without FHA insurance and with HUD servicing released. The offering includes 13 first-lien mortgage notes and one second-lien mortgage note secured by 13 healthcare skilled nursing and assisted living facilities located in eight states. Qualified bidders will have the opportunity to submit competitive, sealed bids for the Mortgage Loans. For bidding purposes, HUD will stratify the loans into pools, grouping them by characteristics such as loan performance, property type, geographic location, and lien position. Pools may contain single or multiple loans. Bidders may submit offers on one or more pools.</P>
                <HD SOURCE="HD1">Bidder Eligibility</HD>
                <P>Eligibility requirements are detailed in the Qualification Statement, which outlines HUD's restrictions on bidding based on prior involvement with the Mortgage Loans. Certain entities and individuals are prohibited from participating in the sale, as described in the Qualification Statement.</P>
                <P>The full loan listing and additional sale details are included in the Bidder's Information Package (BIP), available to qualified bidders upon submission of an acceptable Confidentiality Agreement and Qualification Statement via the bidding platform.</P>
                <HD SOURCE="HD1">Bidding Process</HD>
                <P>The BIP provides detailed instructions on bidding procedures for HLS 2026-2. It will also include a standardized, non-negotiable Loan Sale Agreement that governs the terms of the sale. For access to the BIP and to register for the sale, qualified bidders must submit an executed Confidentiality Agreement and a completed Qualification Statement via the bidding platform.</P>
                <P>As part of its bid, each bidder must submit a minimum deposit of the greater of $100,000 or 10 percent of the aggregate bid prices for all of such bidder's bids. If a bidder's total bid is less than $100,000, the minimum deposit shall be not less than 50 percent of the bidder's aggregate bid. HUD will evaluate all bids and select the successful bid(s) in its sole and absolute discretion. For any winning bidder, the bid deposit becomes non-refundable and will be credited toward the final purchase price. Any deposit amount exceeding the purchase price will be refunded. Deposits submitted by unsuccessful bidders will be returned after notification of the winning bid(s). Closings are expected to occur on or about September 1, 2026.</P>
                <P>The Loan Sale Agreement, included in the BIP, sets forth additional terms and conditions of the sale. To maintain a fair and competitive auction process, neither the bidding procedures nor the Loan Sale Agreement are subject to negotiation.</P>
                <HD SOURCE="HD1">Due Diligence Review</HD>
                <P>The BIP describes the due diligence process for reviewing loan files in HLS 2026-2. Qualified bidders will be able to access loan information electronically. Further information on performing a due diligence review of the Mortgage Loans is provided in the BIP.</P>
                <HD SOURCE="HD1">Mortgage Loan Sale Policy</HD>
                <P>HUD reserves the right to add Mortgage Loans to or delete Mortgage Loans from HLS 2026-2 at any time prior to the award date. HUD also reserves the right to reject bids, in whole or in part, without prejudice against HUD's right to include the Mortgage Loans in a later sale. The Mortgage Loans will not be withdrawn after the award date except as is specifically provided for in the Loan Sale Agreement.</P>
                <P>This is a sale of unsubsidized mortgage loans, pursuant to Section 204(a) of the Departments of Veterans Affairs and Housing and Urban Development, and Independent Agencies Appropriations Act of 1997, (12 U.S.C. 1715z-11a(a)).</P>
                <HD SOURCE="HD1">Mortgage Loan Sale Procedure</HD>
                <P>HUD selected a competitive auction as the method to sell the Mortgage Loans. This method of sale optimizes HUD's return on the sale of these Mortgage Loans, affords the greatest opportunity for all qualified bidders to bid on the Mortgage Loans, and provides the most efficient vehicle for HUD to dispose of the Mortgage Loans.</P>
                <HD SOURCE="HD1">Bidder Eligibility</HD>
                <P>To bid in the sale, a prospective bidder must complete, execute, and submit both a Confidentiality Agreement and a Qualification Statement acceptable to HUD. The following individuals and entities are among those INELIGIBLE to bid on the Mortgage Loans being sold in HLS 2026-2:</P>
                <P>
                    1. A mortgagor or healthcare operator, including its principals, affiliates, family members, and assigns, with 
                    <PRTPAGE P="42554"/>
                    respect to one or more of the Mortgage Loans being offered in the Loan Sale, or an Active Shareholder (as such term is defined in the Qualification Statement);
                </P>
                <P>2. With respect to any other HUD multifamily and/or healthcare mortgage loan not offered in the Loan Sale, any mortgagor or healthcare operator, including any Related Party (as such term is defined in the Qualification Statement) of either, that has failed to file financial statements or is otherwise in default under such mortgage loan or is in violation or noncompliance of any regulatory or business agreements with HUD and that fails to cure such default or violation by no later than the first day of the month of the Bid Date;</P>
                <P>3. Any individual or entity that is debarred, suspended, or excluded from doing business with HUD pursuant to Title 2 of the Code of Federal Regulations, Part 2424;</P>
                <P>4. Any contractor, subcontractor and/or consultant or advisor (including any agent, employee, partner, director, principal or affiliate of any of the foregoing) who performed services for, or on behalf of, HUD in connection with HLS 2026-2;</P>
                <P>5. Any employee of HUD, a member of such employee's family, or an entity owned or controlled by any such employee or member of such an employee's family;</P>
                <P>6. Any individual or entity that uses the services, directly or indirectly, of any person or entity ineligible under provisions (3) through (5) above to assist in preparing its bid on any Mortgage Loan;</P>
                <P>7. An FHA-approved mortgagee, including any principals, affiliates, or assigns thereof, that has received FHA insurance benefits for one or more of the Mortgage Loans being offered in the Loan Sale;</P>
                <P>8. An FHA-approved mortgagee and/or loan servicer, including any principals, affiliates, or assigns thereof, that originated one or more of the Mortgage Loans being offered in the Loan Sale if the Mortgage Loan defaulted within two years of origination and resulted in the payment of an FHA insurance claim;</P>
                <P>9. Any affiliate, principal or employee of any person or entity that, within the two-year period prior to the Bid Date, serviced any Mortgage Loan or performed other services for or on behalf of HUD in regard to any Mortgage Loan;</P>
                <P>10. Any contractor or subcontractor working for or on behalf of HUD that had access to information concerning any Mortgage Loan or provided services to any person or entity which, within the two-year period prior to the Bid Date, had access to information with respect to any Mortgage Loan; and/or</P>
                <P>11. Any employee, officer, director or any other person that provides or will provide services to the prospective bidder with respect to the Mortgage Loans during any warranty period established for the Loan Sale, that serviced the Mortgage Loans or performed other services for or on behalf of HUD or within the two-year period prior to the Bid Date, provided services to any person or entity which serviced, performed services or otherwise had access to information with respect to any Mortgage Loan for or on behalf of HUD.</P>
                <P>Other entities/individuals not described herein may also be restricted from bidding on the Mortgage Loans, as fully detailed in the Qualification Statement.</P>
                <P>The Qualification Statement provides further details pertaining to eligibility requirements. Prospective bidders should carefully review the Qualification Statement to determine whether they are eligible to submit bids on the Mortgage Loans in HLS 2026-2.</P>
                <HD SOURCE="HD1">Freedom of Information Act Requests</HD>
                <P>HUD reserves the right, in its sole and absolute discretion, to disclose information regarding HLS 2026-2, including, but not limited to, the identity of any successful bidder and its bid price or bid percentage for the Mortgage Loans, upon the closing of the sale of the Mortgage Loans. Even if HUD elects not to publicly disclose any information relating to HLS 2026-2, HUD may be required to disclose information relating to HLS 2026-2 pursuant to the Freedom of Information Act and all regulations promulgated thereunder.</P>
                <HD SOURCE="HD1">Scope of Notice</HD>
                <P>This notice applies to HLS 2026-2 and does not establish HUD's policy for the sale of other mortgage loans.</P>
                <SIG>
                    <NAME>Joseph M. Gormley,</NAME>
                    <TITLE>President of the Government National Mortgage Association performing the delegable duties of the Assistant Secretary for Housing—Federal Housing Commissioner.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13814 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-67-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <DEPDOC>[Docket No. FWS-R3-ES-2026-1222; FXES11130300000-267-FF03E00000]</DEPDOC>
                <SUBJECT>Endangered and Threatened Species; Receipt of Recovery Permit Applications</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of receipt of permit applications; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We, the U.S. Fish and Wildlife Service, have received applications for permits to conduct scientific research to promote conservation or other activities intended to enhance the propagation or survival of endangered or threatened species under the Endangered Species Act. We invite the public and local, State, Tribal, and Federal agencies to comment on these applications. Before issuing any of the requested permits, we will take into consideration any information that we receive during the public comment period.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        We must receive your written comments on or before August 10, 2026. Comments submitted electronically using the Federal eRulemaking Portal (see 
                        <E T="02">ADDRESSES</E>
                        , below) must be received by 11:59 p.m. eastern time on the closing date.
                    </P>
                    <P>
                        To ensure your comment is received and considered, you must submit it using one of the methods identified in the 
                        <E T="02">ADDRESSES</E>
                         section of this document. Comments submitted through any method not authorized in this document, or sent to an address not listed here, will not be considered.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P/>
                    <P>
                        <E T="03">Comment submission:</E>
                         All submissions must include the docket number [FWS-R3-ES-2026-1222] for this document. You must submit comments using one of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Electronic submission:</E>
                         Federal eRulemaking Portal at: 
                        <E T="03">https://www.regulations.gov.</E>
                         In the Search box, enter FWS-R3-ES-2026-1222, which is the docket number for this action. Then click the Search button. On the resulting page, you may submit a comment by clicking on “Comment.” Please ensure that you have found the correct document before submitting your comments.
                    </P>
                    <P>
                        • 
                        <E T="03">U.S. mail:</E>
                         Public Comments Processing, Attn: Docket No. FWS-R3-ES-2026-1222, Policy and Regulations Branch, U.S. Fish and Wildlife Service, MS: PRB (JAO/3W), 5275 Leesburg Pike, Falls Church, VA 22041-3803.
                        <PRTPAGE P="42555"/>
                    </P>
                    <P>Comments submitted through any method not authorized in this document, or sent to an address not listed here, will not be considered. We will not accept comments via email, fax, or hand delivery. We are not required to consider comments that are submitted after the comment period ends or that are submitted via a method outside of these instructions. Comments containing profanity, vulgarity, threats, or other inappropriate content will not be considered.</P>
                    <P>
                        We will post all comments at 
                        <E T="03">https://www.regulations.gov.</E>
                         You may request that we withhold personal identifying information from public review; however, we cannot guarantee that we will be able to do so. See Public Availability of Comments for more information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Nathan Rathbun, 612-713-5343 (phone); 
                        <E T="03">permitsR3ES@fws.gov</E>
                         (email). Submit requests for copies of the applications and related documents, by one of these methods. All requests should specify the applicant name(s) and application number(s) (
                        <E T="03">e.g.,</E>
                         ESXXXXXX; see table in 
                        <E T="02">SUPPLEMENTARY INFORMATION</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. 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>
                    We, the U.S. Fish and Wildlife Service, invite review and comment from the public and local, State, Tribal, and Federal agencies on applications we have received for permits to conduct certain activities with endangered and threatened species under section 10(a)(1)(A) of the Endangered Species Act of 1973, as amended (ESA; 16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ), and our regulations in the Code of Federal Regulations (CFR) at 50 CFR part 17. Documents and other information submitted with the applications are available for review, subject to the requirements of the Privacy Act and the Freedom of Information Act.
                </P>
                <HD SOURCE="HD1">Background</HD>
                <P>The ESA prohibits certain activities with endangered and threatened species unless authorized by a Federal permit. The ESA and our implementing regulations in part 17 of title 50 of the CFR provide for the issuance of such permits and require that we invite public comment before issuing permits for activities involving endangered species.</P>
                <P>A recovery permit issued by us under section 10(a)(1)(A) of the ESA authorizes the permittee to conduct activities with endangered species for scientific purposes that promote recovery or for enhancement of propagation or survival of the species. Our regulations implementing section 10(a)(1)(A) for these permits are found at 50 CFR 17.22 for endangered wildlife species, 50 CFR 17.32 for threatened wildlife species, 50 CFR 17.62 for endangered plant species, and 50 CFR 17.72 for threatened plant species.</P>
                <HD SOURCE="HD1">Permit Applications Available for Review and Comment</HD>
                <P>The ESA requires that we invite public comment before issuing these permits. Accordingly, we invite local, State, Tribal, and Federal agencies and the public to submit written data, views, or arguments with respect to these applications. The comments and recommendations that will be most useful and likely to influence agency decisions are those supported by quantitative information or studies. Proposed activities in the following permit requests are for the recovery and enhancement of propagation or survival of the species in the wild.</P>
                <GPOTABLE COLS="7" OPTS="L2,nj,tp0,p7,7/8,i1" CDEF="s40,r35,r100,r50,r50,r50,r25">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Application No.</CHED>
                        <CHED H="1">Applicant</CHED>
                        <CHED H="1">Species</CHED>
                        <CHED H="1">Location</CHED>
                        <CHED H="1">Activity</CHED>
                        <CHED H="1">Type of take</CHED>
                        <CHED H="1">
                            Permit
                            <LI>action</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">ESPER30276997</ENT>
                        <ENT>Stephanie Bien, Cincinnati, OH</ENT>
                        <ENT>
                            Indiana bat (
                            <E T="03">Myotis sodalis</E>
                            ), gray bat (
                            <E T="03">M. grisescens</E>
                            ), northern long-eared bat (
                            <E T="03">M. septentrionalis</E>
                            ), tricolored bat (
                            <E T="03">Perimyotis subflavus</E>
                            ), Ozark big-eared bat (
                            <E T="03">Corynorhinus townsendii ingens</E>
                            ), and Virginia big-eared bat (
                            <E T="03">C. townsendii virginianus</E>
                            )
                        </ENT>
                        <ENT>AL, AR, CT, CO, DE, DC, FL, GA, IL, IN, IA, KS, KY, LA, ME, MD, MA, MI, MN, MS, MO, MT, NE, NH, NJ, NY, NM, NC, ND, OH, OK, PA, RI, SC, SD, TN, TX, VT, VA, WV, WI, WY</ENT>
                        <ENT>Conduct presence/absence surveys, document habitat use, conduct population monitoring, and evaluate impacts</ENT>
                        <ENT>Capture, handle, band, radiotelemetry, release</ENT>
                        <ENT>New.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ES75401D</ENT>
                        <ENT>U.S. Geological Survey, La Crosse, WI</ENT>
                        <ENT>
                            Winged mapleleaf (
                            <E T="03">Quadrula fragosa</E>
                            ), snuffbox (
                            <E T="03">Epioblasma triquetra</E>
                            ), spectaclecase (
                            <E T="03">Cumberlandia monodonta</E>
                            ), Higgins' eye pearlymussel (
                            <E T="03">Lampsilis higginsii</E>
                            ), and sheepnose (
                            <E T="03">Plethobasus cyphyus</E>
                            )
                        </ENT>
                        <ENT>IA, MN, WI</ENT>
                        <ENT>Conduct presence/absence surveys, document habitat use, conduct population monitoring, and evaluate impacts</ENT>
                        <ENT>Collect, mark, release, captive rear</ENT>
                        <ENT>Renew and amend.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ESPER19855675</ENT>
                        <ENT>Aimee-Christine Bjornstad, Elkhart, IN</ENT>
                        <ENT>
                            Add new species: gray bat (
                            <E T="03">Myotis grisescens</E>
                            )—to existing authorized species: Indiana bat (
                            <E T="03">M. sodalis</E>
                            ) and northern long-eared bat (
                            <E T="03">M. septentrionalis</E>
                            )
                        </ENT>
                        <ENT>Add new states: IN, IL, MO—to existing authorized states: IA, MI, OH, PA, WV</ENT>
                        <ENT>Conduct presence/absence surveys, document habitat use, conduct population monitoring, and evaluate impacts</ENT>
                        <ENT>Capture, handle, radiotelemetry, band, release</ENT>
                        <ENT>Amend.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ESPER30623424</ENT>
                        <ENT>United States Geological Survey—Columbia Ecological Research Center, Columbia, MO</ENT>
                        <ENT>
                            Rayed bean (
                            <E T="03">Villosa fabalis</E>
                            ), northern riffleshell (
                            <E T="03">Epioblasma rangiana</E>
                            ), and snuffbox (
                            <E T="03">Epioblasma triquetra</E>
                            )
                        </ENT>
                        <ENT>MI, OH, MO</ENT>
                        <ENT>Conduct presence/absence surveys, document habitat use, conduct population monitoring, and evaluate impacts</ENT>
                        <ENT>Collect, temporarily hold, captive rear, release</ENT>
                        <ENT>New.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42556"/>
                        <ENT I="01">ES38842A</ENT>
                        <ENT>Sanders Environmental Inc., Bellefonte, PA</ENT>
                        <ENT>
                            Indiana bat (
                            <E T="03">Myotis sodalis</E>
                            ), gray bat (
                            <E T="03">M. grisescens</E>
                            ), northern long-eared bat (
                            <E T="03">M. septentrionalis</E>
                            ), Ozark big-eared bat (
                            <E T="03">Corynorhinus townsendii ingens</E>
                            ), and Virginia big-eared bat (
                            <E T="03">C. t. virginianus</E>
                            )
                        </ENT>
                        <ENT>Add new states: CT, DE, DC, ME, MD, MA, NH, NJ, NY, PA, RI, VT, VA, WV—to existing authorized states: AL, AR, FL, GA, IL, IN, IA, KS, KY, LA, MI, MN, MS, MO, MT, NE, NC, ND, OK, OH, SC, SD, TN, TX, WI, WY</ENT>
                        <ENT>Conduct presence/absence surveys, document habitat use, conduct population monitoring, and evaluate impacts</ENT>
                        <ENT>Capture, handle, radiotelemetry, band, biosample, release</ENT>
                        <ENT>Renew and amend.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ESPER30823529</ENT>
                        <ENT>Liesel Fenstermaker, Akron, OH</ENT>
                        <ENT>15 freshwater mussel species</ENT>
                        <ENT>IA, IL, IN, MI, MN, MO, NY, KY, OH, PA, WV, WI</ENT>
                        <ENT>Conduct presence/absence surveys, document habitat use, conduct population monitoring, and evaluate impacts</ENT>
                        <ENT>Capture, handle, tag, relocate, release</ENT>
                        <ENT>New.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ES65584D</ENT>
                        <ENT>Ian Pearse, Fort Collins, CO</ENT>
                        <ENT>
                            Rusty patched bumble bee (
                            <E T="03">Bombus affinis</E>
                            )
                        </ENT>
                        <ENT>IL, IN, IA, MI, MN, OH, VA, WI</ENT>
                        <ENT>Conduct presence/absence surveys, document habitat use, conduct population monitoring, and evaluate impacts</ENT>
                        <ENT>Capture, handle, release, biosample, mark</ENT>
                        <ENT>Renew.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ESPER30958222</ENT>
                        <ENT>U.S. Forest Service—Huron Manistee National Forest, Mio, MI</ENT>
                        <ENT>
                            Hungerford's crawling water beetle (
                            <E T="03">Brychius hungerfordi</E>
                            )
                        </ENT>
                        <ENT>MI</ENT>
                        <ENT>Conduct presence/absence surveys, document habitat use, conduct population monitoring, and evaluate impacts</ENT>
                        <ENT>Capture, handle, release</ENT>
                        <ENT>New.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ESPER30969571</ENT>
                        <ENT>Scott LaValley, Stow, OH</ENT>
                        <ENT>22 freshwater mussel species</ENT>
                        <ENT>IN, IL, IA, KY, MI, MN, NY, NC, OH, PA, TN, VA, WV, WI</ENT>
                        <ENT>Conduct presence/absence surveys, document habitat use, conduct population monitoring, and evaluate impacts</ENT>
                        <ENT>Capture, handle, release, mark, tag, relocate</ENT>
                        <ENT>New.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ESPER31016145</ENT>
                        <ENT>Endangered Resource Services, LLC, Saint Croix Falls, WI</ENT>
                        <ENT>
                            Higgins' eye pearlymussel (
                            <E T="03">Lampsilis higginsii</E>
                            ), sheepnose (
                            <E T="03">Plethobasus cyphyus</E>
                            ), spectaclecase (
                            <E T="03">Cumberlandia monodonta</E>
                            ), snuffbox (
                            <E T="03">Epioblasma triquetra</E>
                            ), and winged mapleleaf (
                            <E T="03">Quadrula fragosa</E>
                            )
                        </ENT>
                        <ENT>MN, WI</ENT>
                        <ENT>Conduct presence/absence surveys, document habitat use, conduct population monitoring, and evaluate impacts</ENT>
                        <ENT>Capture, handle, release</ENT>
                        <ENT>New.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ESPER31458452</ENT>
                        <ENT>Brandon Yates, Galloway, OH</ENT>
                        <ENT>
                            Blackside dace (
                            <E T="03">Phoxinus cumberlandensis</E>
                            ) and 22 freshwater mussel species
                        </ENT>
                        <ENT>AL, AR, CT, DE, GA, IL, IN, IA, KY, KS, LA, MD, MA, MI, MN, MO, MS, NH, NJ, NY, NE, NC, OK, OH, PA, SD, TN, VT, VA, WV, WI</ENT>
                        <ENT>Conduct presence/absence surveys, document habitat use, conduct population monitoring, and evaluate impacts</ENT>
                        <ENT>Capture, handle, release, relocate</ENT>
                        <ENT>New.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Public Availability of Comments</HD>
                <P>Written comments we receive become part of the administrative record associated with this action. Before including your address, phone number, email address, or other personal identifying information in your comment, you should be aware that your entire comment—including your personal identifying information—may be made publicly available at any time. While you can request in your comment that we withhold your personal identifying information from public review, we cannot guarantee that we will be able to do so. Moreover, all submissions from organizations or businesses, and from individuals identifying themselves as representatives or officials of organizations or businesses, will be made available for public disclosure in their entirety.</P>
                <HD SOURCE="HD1">Next Steps</HD>
                <P>
                    If we decide to issue permits to any of the applicants listed in this notice, we will publish a notice in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">Authority</HD>
                <P>We publish this notice under section 10(c) of the Endangered Species Act of 1973, as amended (16 U.S.C. 1539(c)).</P>
                <SIG>
                    <NAME>Karen Herrington,</NAME>
                    <TITLE>Acting Assistant Regional Director, Ecological Service, Midwest Region.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13850 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4333-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="42557"/>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <DEPDOC>[Docket No. FWS-R4-ES-2026-2179; FXES11140400000-267-FF04EF4000]</DEPDOC>
                <SUBJECT>Receipt of Incidental Take Permit Application and Proposed Habitat Conservation Plan for the Sand Skink; Orange County, FL; Categorical Exclusion</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability; request for comments and information.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We, the Fish and Wildlife Service (Service), announce receipt of an application from Sutton Grande, LLC (Sutton Grande Project) (applicant) for an incidental take permit (ITP) under the Endangered Species Act (ESA). The applicant requests the ITP to take the federally listed threatened sand skink incidental to the construction of a residential development and the associated clearing and infrastructure in Orange County, Florida. We request public comment on the application, which includes the applicant's proposed Habitat Conservation Plan (HCP), and on the Service's preliminary determination that the proposed permitting action may be eligible for a categorical exclusion pursuant to the National Environmental Policy Act (NEPA), the Department of the Interior's (DOI) NEPA regulations, and the DOI Departmental Manual. To make this preliminary determination, we prepared a draft screening form and NEPA statement for HCPs, which are available for public review. We invite comment from the public and local, State, Tribal, and Federal agencies.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive your written comments on or before August 10, 2026.</P>
                    <P>
                        To ensure your comment is received and considered, you must submit it using one of the methods identified in the 
                        <E T="02">ADDRESSES</E>
                         section of this document. Comments submitted through any method not authorized in this document, or sent to an address not listed here, will not be considered.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        <E T="03">Obtaining Documents:</E>
                         The documents this notice announces, as well as any comments and other materials that we receive, will be available for public inspection online in Docket No. FWS-R4-ES-2026-2179 at 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">Submitting Comments:</E>
                         All submissions must include the docket number [FWS-R4-ES-2026-2179] for this document. You must submit comments using one of the following methods:
                    </P>
                    <P>
                        • 
                        <E T="03">Online: https://www.regulations.gov.</E>
                         Follow the instructions for submitting comments on Docket No. FWS-R4-ES-2026-2179.
                    </P>
                    <P>
                        • 
                        <E T="03">U.S. mail:</E>
                         For public comments processing, Attn: Docket No. FWS-R4-ES-2026-2179; U.S. Fish and Wildlife Service, MS: PRB/3W; 5275 Leesburg Pike; Falls Church, VA 22041-3803.
                    </P>
                    <P>Comments submitted through any method not authorized in this document, or sent to an address not listed here, will not be considered. We will not accept comments via email, fax, or hand delivery. We are not required to consider comments that are submitted after the comment period ends or that are submitted via a method outside of these instructions. Comments containing profanity, vulgarity, threats, or other inappropriate content will not be considered.</P>
                    <P>
                        We will post all comments at 
                        <E T="03">https://www.regulations.gov.</E>
                         You may request that we withhold personal identifying information from public review; however, we cannot guarantee that we will be able to do so. See Public Availability of Comments for more information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Erin Gawera, Jacksonville Ecological Services Field Office, by phone at 904-404-2464 or via email at 
                        <E T="03">erin_gawera@fws.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. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The U.S. Fish and Wildlife Service (Service), announces receipt of an application from Sutton Grande, LLC (Sutton Grande Project) (applicant) for an Incidental Take Permit (ITP) under the Endangered Species Act of 1973, as amended (ESA; (16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ). The applicant requests the ITP to take the federally listed threatened sand skink (
                    <E T="03">Neopseps</E>
                     (=
                    <E T="03">Plestiodon</E>
                    ) 
                    <E T="03">reynoldsi</E>
                    ) incidental to the construction of a residential development and the associated clearing and infrastructure in Orange County, Florida.
                </P>
                <P>
                    We request public comment on the application, which includes the applicant's HCP, and on the Service's preliminary determination that this proposed ITP may qualify for a categorical exclusion pursuant to the National Environmental Policy Act (NEPA; 42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), the Department of the Interior's (DOI) NEPA regulations (43 CFR part 46), and the DOI's Departmental Manual (DM; 516 DM 8.5(C)(2)). To make this preliminary determination, we prepared a draft screening form and NEPA statement for Habitat Conservation Plans (HCP), both of which are available for public review.
                </P>
                <HD SOURCE="HD1">Proposed Project</HD>
                <P>The applicant requests a 5-year ITP to take skinks via the conversion of approximately 5.94 acres (ac) of occupied nesting, foraging, and sheltering skink habitat incidental to the construction and operation of a residential development on 13.56 ac, located at 13.56331 Avalon Road, City of Winter Garden, Section 31, Township 24 South, Range 27 East, Orange County, Florida.</P>
                <P>The applicant proposes to mitigate for take of the skinks by purchasing credits equivalent to 11.88-ac of skink-occupied habitat within the Collany Conservation Bank or another Service approved skink conservation bank. The Service would require the applicant to purchase the credits prior to engaging in any phase of the project.</P>
                <HD SOURCE="HD1">Our Preliminary Determination</HD>
                <P>The Service has made a preliminary determination that the reasonably foreseeable effects of the applicant's proposed project, including the construction of a residential development and the associated clearing and infrastructure, would have minor impacts on skinks and the human environment and that extraordinary circumstances in 43 CFR 46.215 do not apply. Reasonably foreseeable effects encompass those resulting from implementation of the action together with other past, present, and reasonably foreseeable future effects.</P>
                <P>Therefore, we have preliminarily determined that the proposed ESA section 10(a)(1)(B) permit would be a low-effect ITP that may qualify for application of a categorical exclusion (516 DM 8.5(C)(2)), pursuant to NEPA, the DOI's NEPA regulations, and the DOI DM. A low-effect ITP is one that would result in (1) negligible or minor individual or cumulative effects on species covered in the HCP; (2) no significant effect on the human environment; and (3) reasonably foreseeable effects that would not result in significant effects to the human environment.</P>
                <HD SOURCE="HD1">Next Steps</HD>
                <P>
                    The Service will evaluate the application and the comments to determine whether to issue the requested ITP. We will also conduct an intra-Service consultation pursuant to 
                    <PRTPAGE P="42558"/>
                    section 7 of the ESA to evaluate the effects of the proposed take. After considering the preceding and other matters, we will determine whether the permit issuance criteria of section 10(a)(1)(B) of the ESA have been met. If met, the Service will issue ITP number PER30119893 to Sutton Grande, LLC. (Sutton Grande Project).
                </P>
                <HD SOURCE="HD1">Public Availability of Comments</HD>
                <P>
                    Before including your address, phone number, email address, or other personal identifying information in your comment, be aware that your entire comment, including your personal identifying information, may be made available to the public. If you submit a comment at 
                    <E T="03">https://www.regulations.gov,</E>
                     your entire comment, including any personal identifying information, will be posted on the website. If you submit a hard copy comment that includes personal identifying information, such as your address, phone number, or email address, you may request at the top of your document that we withhold this information from public review. However, we cannot guarantee that we will be able to do so. Moreover, all submissions from organizations or businesses, and from individuals identifying themselves as representatives or officials of organizations or businesses, will be made available for public disclosure in their entirety.
                </P>
                <HD SOURCE="HD1">Authority</HD>
                <P>
                    The Service provides this notice under section 10(c) of the Endangered Species Act (16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) and its implementing regulations (50 CFR 17.32), National Environmental Policy Act (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), as amended, and the Department of Interior's implementing regulations (43 CFR part 46).
                </P>
                <SIG>
                    <NAME>Jose Rivera,</NAME>
                    <TITLE>Manager, Division of Environmental Review, Florida Ecological Services Field Office, U.S. Fish and Wildlife Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13852 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4333-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[A2407-014-004-065516, #O2509-014-004-125222]</DEPDOC>
                <SUBJECT>Civil Monetary Penalties for Onshore Oil and Gas Operations and Coal Trespass</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of annual civil penalties adjustments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice restates the amounts of civil monetary penalties contained in the Bureau of Land Management's (BLM) regulations governing onshore oil and gas operations and coal trespass. For 2026, the BLM will not update its civil monetary penalties and will continue to use the civil monetary penalty levels currently in its regulations. This notice is required by the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 and is consistent with applicable Office of Management and Budget (OMB) guidance.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For information regarding the BLM's Fluid Minerals Program, please contact John Ajak, Acting Division Chief, Fluid Minerals Division, telephone: 505-549-9654; email: 
                        <E T="03">jajak@blm.gov.</E>
                         For information regarding the BLM's Solid Minerals Program, please contact Indra Dahal, Acting Division Chief, Solid Minerals Division, telephone: 571-458-6637; email: 
                        <E T="03">idahal@blm.gov.</E>
                    </P>
                    <P>Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On November 2, 2015, the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015 (Sec. 701, Pub. L. 114-74) (the 2015 Act) became law, amending the Federal Civil Penalties Inflation Adjustment Act of 1990 (Pub. L. 101-410).</P>
                <P>On an annual basis, the 2015 Act requires agencies to:</P>
                <P>1. Adjust the level of civil monetary penalties for inflation based on Consumer Price Index (CPI-U) data from the Bureau of Labor Statistics (BLS); and</P>
                <P>2. Report inflation adjustments in the Agency Financial Reports as directed by OMB Circular A-136, or any successor thereto.</P>
                <P>On April 17, 2026, OMB issued Memorandum M-26-11, entitled “Cancellation of Penalty Inflation Adjustments for 2026, Regarding the Federal Civil Penalties Inflation Adjustment Act Improvements Act of 2015.” In that guidance, OMB cancelled the inflation adjustment for 2026 based on the lack of October 2025 CPI-U data, which is needed to make adjustments under the 2015 Act. The guidance directed agencies to continue using the 2025 civil monetary penalty levels.</P>
                <P>Based on Memorandum M-26-11, the BLM has issued this notice to affirm the following civil penalties:</P>
                <GPOTABLE COLS="3" OPTS="L2,nj,tp0,i1" CDEF="s50,r50,12">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">CFR citation</CHED>
                        <CHED H="1">Description of the penalty</CHED>
                        <CHED H="1">
                            Current
                            <LI>penalty</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">43 CFR 3163.2(b)(1)</ENT>
                        <ENT>Failure to comply</ENT>
                        <ENT>$1,368</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">43 CFR 3163.2(b)(2)</ENT>
                        <ENT>If corrective action is not taken</ENT>
                        <ENT>13,690</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">43 CFR 3163.2(d)</ENT>
                        <ENT>If transporter fails to permit inspection for documentation</ENT>
                        <ENT>1,368</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">43 CFR 3163.2(e)</ENT>
                        <ENT>Failure to permit inspection, failure to notify</ENT>
                        <ENT>27,378</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">43 CFR 3163.2(f)</ENT>
                        <ENT>False or inaccurate documents; unlawful transfer or purchase</ENT>
                        <ENT>68,445</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">43 CFR 9239.5-3(f)(1)</ENT>
                        <ENT>Coal exploration for commercial purposes without an exploration license</ENT>
                        <ENT>5,125</ENT>
                    </ROW>
                </GPOTABLE>
                <EXTRACT>
                    <FP>(Authority: 25 U.S.C. 396d and 2107; 30 U.S.C. 189, 306, 359, and 1751; 43 U.S.C. 1732(b), 1733, 1740; R.S. 2478; 43 U.S.C. 1201; and Sec. 701, Pub. L. 114-74, 129 Stat. 599, unless otherwise noted.)</FP>
                </EXTRACT>
                <SIG>
                    <PRTPAGE P="42559"/>
                    <NAME>Tina Roberts-Ashby,</NAME>
                    <TITLE>Acting Assistant Director, Energy, Minerals and Realty Management.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13896 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4331-29-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation No. 731-TA-1738 (Final)]</DEPDOC>
                <SUBJECT>Polypropylene Corrugated Boxes From Vietnam; Determination</SUBJECT>
                <P>
                    On the basis of the record 
                    <SU>1</SU>
                    <FTREF/>
                     developed in the subject investigation, the United States International Trade Commission (“Commission”) determines, pursuant to the Tariff Act of 1930 (“the Act”), that an industry in the United States is materially injured by reason of imports of polypropylene corrugated boxes (“PC boxes”) from Vietnam, provided for in subheading 3923.10.90 of the Harmonized Tariff Schedule of the United States, that have been found by the U.S. Department of Commerce (“Commerce”) to be sold in the United States at less than fair value (“LTFV”).
                    <E T="51">2 3</E>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The record is defined in § 207.2(f) of the Commission's Rules of Practice and Procedure (19 CFR 207.2(f)).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         91 FR 29457 (May 20, 2026).
                    </P>
                    <P>
                        <SU>3</SU>
                         The Commission also finds that imports subject to Commerce's affirmative critical circumstances determination are not likely to undermine seriously the remedial effect of the antidumping duty order on Vietnam.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The Commission instituted this investigation effective March 18, 2025, following receipt of petitions filed with the Commission and Commerce by CoolSeal USA Inc., Perrysburg, Ohio; Inteplast Group Corporation, Livingston, New Jersey; SeaCa Plastic Packaging, Kent, Washington; and Technology Container Corp., Desoto, Texas, alleging that an industry in the United States is materially injured and threatened with material injury by reason of subsidized imports of PC from China and LTFV imports of PC boxes from China and Vietnam. The Commission scheduled the final phase of the investigation following notification of preliminary determinations by Commerce that imports of PC boxes from China were being sold at LTFV within the meaning of 733(b) of the Act (19 U.S.C. 1673b(b)) and subsidized within the meaning of section 703(b) of the Act (19 U.S.C. 1671b(b)). Notice of the scheduling of the final phase of the Commission's investigations and of a public hearing to be held in connection therewith was given by posting copies of the notice in the Office of the Secretary, U.S. International Trade Commission, Washington, DC, and by publishing the notice in the 
                    <E T="04">Federal Register</E>
                     on August 26, 2025 (90 FR 41595).
                    <SU>4</SU>
                    <FTREF/>
                     The public hearing in connection with the investigations, scheduled for January 21, 2026, was cancelled.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Due to the lapse in appropriations and ensuing cessation of Commission operations, the Commission tolled its schedule for this proceeding. The schedule was revised in subsequent notices published in the 
                        <E T="04">Federal Register</E>
                         on November 26, 2025 (90 FR 54369) and December 18, 2025 (90 FR 59202).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         91 FR 2800 (January 22, 2026).
                    </P>
                </FTNT>
                <P>
                    The investigation schedules became staggered when Commerce did not align its antidumping duty investigation with respect to PC boxes from Vietnam with its antidumping and countervailing duty investigations with respect to PC boxes from China and reached earlier final determinations on imports of PC boxes from China. On March 9, 2026, the Commission issued final affirmative determinations in its antidumping and countervailing duty investigations of PC boxes from China (91 FR 11988, March 11, 2026). Following notification of a final determination by Commerce that imports of PC boxes from Vietnam were being sold at LTFV within the meaning of section 735(a) of the Act (19 U.S.C. 1673d(a)), notice of the supplemental scheduling of the final phase of the Commission's antidumping duty investigation with respect to PC boxes from Vietnam was given by posting copies of the notice in the Office of the Secretary, U.S. International Trade Commission, Washington, DC, and by publishing the notice in the 
                    <E T="04">Federal Register</E>
                     of May 29, 2026 (91 FR 32093).
                </P>
                <P>
                    The Commission made this determination pursuant to § 735(b) of the Act (19 U.S.C. 1673d(b)). It completed and filed its determination in this investigation on July 6, 2026. The views of the Commission are contained in USITC Publication 5759 (July 2026), entitled 
                    <E T="03">Polypropylene Corrugated Boxes from Vietnam: Investigation No. 731-TA-1738 (Final).</E>
                </P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: July 6, 2026.</DATED>
                    <NAME>Lisa Barton,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13819 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation Nos. 701-TA-760, 701-TA-762, 731-TA-1744, 731-TA-1746 (Final)]</DEPDOC>
                <SUBJECT>Silicon Metal From Australia and Norway; Supplemental Schedule for the Final Phase of the Investigations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>United States International Trade Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>June 30, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Gregory Gutierrez ((202) 205-1999), 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 proceeding 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>
                    Effective September 25, 2025, the Commission established a general schedule for the conduct of the final phase of its investigations on silicon metal from Angola, Laos, Thailand, Australia, and Norway (90 FR 54365, November 26, 2025) following preliminary determinations by the U.S. Department of Commerce (“Commerce”) that imports of silicon metal from Laos and Thailand were being subsidized by the government of Laos and Thailand (90 FR 46384 and 90 FR 46388, September 26, 2025) and imports of silicon metal from Angola and Laos were being sold in the United States at less than fair value (“LTFV”) (90 FR 46807 and 90 FR 46810, September 30, 2025). Notice of the scheduling of the final phase of the Commission's investigations and of a public hearing to be held in connection therewith was given by posting copies of the notice in the Office of the Secretary, U.S. International Trade Commission, Washington, DC, and by publishing the notice in the 
                    <E T="04">Federal Register</E>
                     on November 26, 2025 (90 FR 54365).
                    <SU>1</SU>
                    <FTREF/>
                     All persons who requested the 
                    <PRTPAGE P="42560"/>
                    opportunity were permitted to participate.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Due to the lapse in appropriations and ensuing cessation of Commission operations, the Commission tolled its schedule for this proceeding. The schedule was revised in a subsequent notice 
                        <PRTPAGE/>
                        published in the 
                        <E T="04">Federal Register</E>
                         on December 16, 2025 (90 FR 58308)
                    </P>
                </FTNT>
                <P>
                    On February 23, 2026, Commerce published in the 
                    <E T="04">Federal Register</E>
                     its final affirmative countervailing duty determinations with respect to silicon metal from Laos and Thailand (91 FR 8425 and 91 FR 8436, February 23, 2026) and antidumping duty determinations with respect to silicon metal from Angola and Laos (91 FR 8407 and 91 FR 8419, February 23, 2026). The Commission subsequently issued its final determinations that an industry in the United States was material injured by reason of imports of silicon metal from Laos that were found by Commerce to be sold in the United States at LTFV and subsidized by the government of Laos. The Commission also determined that an industry in the United States was threatened with materially injured by reason of imports of silicon metal from Angola that were found by Commerce to be sold in the United States at LTFV. The Commission further determined that imports of silicon metal from Thailand found by Commerce to be subsidized by the government of Thailand were negligible and terminated the countervailing duty investigation concerning Thailand. (91 FR 18004, April 9, 2026).
                </P>
                <P>
                    On June 30, 2025, Commerce published in the 
                    <E T="04">Federal Register</E>
                     its final affirmative countervailing duty and antidumping duty determinations with respect to imports of silicon metal from Australia and Norway (91 FR 39593, 91 FR 39597, 91 FR 39598, and 91 FR 39601, June 30, 2026). Accordingly, the Commission currently is issuing a supplemental schedule for the final phase of its investigations on imports of silicon metal from Australia and Norway.
                </P>
                <P>
                    <E T="03">This supplemental schedule is as follows:</E>
                     the deadline for filing supplemental party comments on Commerce's final antidumping and countervailing duty determinations is 5:15 p.m. on July 10, 2026. Supplemental party comments may address only Commerce's final determinations regarding imports of silicon metal from Australia and Norway. These supplemental final comments may not contain new factual information and may not exceed five (5) pages in length. The supplemental staff report in the final phase of this proceeding will be placed in the nonpublic record on July 27, 2026, and a public version will be issued thereafter.
                </P>
                <P>For further information concerning this proceeding see the Commission's notice cited above and the Commission's Rules of Practice and Procedure, part 201, subparts A and B (19 CFR part 201), and part 207, subparts A and C (19 CFR part 207).</P>
                <P>Additional written submissions to the Commission, including requests pursuant to section 201.12 of the Commission's rules, shall not be accepted unless good cause is shown for accepting such submissions, or unless the submission is pursuant to a specific request by a Commissioner or Commission staff.</P>
                <P>In accordance with sections 201.16(c) and 207.3 of the Commission's rules, each document filed by a party to the proceeding must be served on all other parties to the proceeding (as identified by either the public or BPI 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>
                    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>
                    <E T="03">Authority:</E>
                     This proceeding is being conducted under authority of title VII of the Tariff Act of 1930; this notice is published pursuant to section 207.21 of the Commission's rules.
                </P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: July 7, 2026.</DATED>
                    <NAME>Lisa Barton,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13891 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Federal Bureau of Investigation</SUBAGY>
                <DEPDOC>[Docket No. FBI164]</DEPDOC>
                <SUBJECT>FBI Criminal Justice Information Services Division; User Fee Schedule; Correction</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Bureau of Investigation (FBI), Justice.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; correction.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Federal Bureau of Investigation published a document in the 
                        <E T="04">Federal Register</E>
                         of June 8, 2026, concerning the Criminal Justice Information Services Division User Fee Schedule. The document was published without including the footnotes for the new fee amounts table.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Mark Bland, Chief, Financial Management Unit, Resources Management Section, Criminal Justice Information Services (CJIS) Division, FBI, 1000 Custer Hollow Road, Module D-3, Clarksburg, WV 26306. Telephone number 771-228-3066.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Correction</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of June 8, 2026, in FR Doc. 91-109, on page 34655, immediately following the FINGERPRINT-BASED CHRI CHECKS table, add the footnotes to read:
                </P>
                <EXTRACT>
                    <P>
                        <SU>1</SU>
                         Centralized Billing Service Providers, see 75 
                        <E T="03">FR</E>
                         18753.
                    </P>
                    <P>
                        <SU>2</SU>
                         Cost Recovery = $3; Automation = $10.
                    </P>
                    <P>
                        <SU>3</SU>
                         Volunteers providing care for children, the elderly, or individuals with disabilities. See 
                        <E T="03">e.g.,</E>
                         75 
                        <E T="03">FR</E>
                         18752, 83 
                        <E T="03">FR</E>
                         48335.
                    </P>
                    <P>
                        <SU>4</SU>
                         Cost Recovery = $3; Automation = $8.
                    </P>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: July 7, 2026.</DATED>
                    <NAME>Timothy A. Ferguson,</NAME>
                    <TITLE>Assistant Director.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13886 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">LEGAL SERVICES CORPORATION</AGENCY>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE:</HD>
                    <P>The Institutional Advancement Committee of the Legal Services Corporation (LSC) Board of Directors will meet on July 17, 2026. The meeting will begin at 11:30 a.m. Eastern Time and continue until the conclusion of the Committee's agenda.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE:</HD>
                    <P>Public Notice of Virtual Meeting.</P>
                    <P>LSC will conduct its July 17, 2026, meeting virtually via videoconference.</P>
                    <P>
                        <E T="03">Public Observation:</E>
                         Unless otherwise noted herein, the committee meeting will be open to public observation via LSC's YouTube channel: 
                        <E T="03">https://www.youtube.com/@LegalServicesCorp/streams.</E>
                    </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS:</HD>
                    <P>Open, except that, upon a vote of the Board of Directors, the meeting may be closed to the public to consider and act on the approval of invitees to the Leaders Council and Emerging Leaders Council.</P>
                    <P>Any portion of the closed sessions consisting solely of briefings does not fall within the Sunshine Act's definition of the term “meeting” and, therefore, the requirements of the Sunshine Act do not apply to such portion of the closed session.</P>
                    <P>
                        A verbatim written transcript will be made of the closed session of the Institutional Advancement Committee. 
                        <PRTPAGE P="42561"/>
                        The transcript of any portions of the closed session falling within the relevant provisions of the Government in the Sunshine Act, 5 U.S.C. 552b(c)(6), (7), (9) and (10), will not be available for public inspection. A copy of the General Counsel's certification that, in his opinion, the closing is authorized by law will be available upon request.
                    </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P/>
                </PREAMHD>
                <HD SOURCE="HD1">Meeting Schedule</HD>
                <HD SOURCE="HD2">1. Friday, July 17, 2026—Institutional Advancement Committee Meeting</HD>
                <HD SOURCE="HD3">Start Time—11:30 a.m. ET</HD>
                <FP SOURCE="FP-2">a. Matters to be discussed include a Chairman's Report and update on the Leaders Council and Emerging Leaders Council; a development update; privately funded project highlights; and a strategic communications and social media update</FP>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION: </HD>
                    <P>
                        Kimberly Little, Board and Executive Coordinator, at (202) 295-1500. Questions may also be sent by electronic mail to the Office of the Corporate Secretary at 
                        <E T="03">updates@lsc.gov.</E>
                    </P>
                    <P>
                        <E T="03">Non-Confidential Meeting Materials:</E>
                         Non-confidential meeting materials will be made available in electronic format at least 24 hours in advance of the meeting on the LSC website, at 
                        <E T="03">https://www.lsc.gov/about-lsc/board-meeting-materials.</E>
                    </P>
                </PREAMHD>
                <EXTRACT>
                    <FP>(Authority: 5 U.S.C. 552b.)</FP>
                </EXTRACT>
                <SIG>
                    <DATED> Dated: July 7, 2026.</DATED>
                    <NAME>Stefanie Davis,</NAME>
                    <TITLE>Deputy General Counsel, Legal Services Corporation.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13889 Filed 7-7-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 7050-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL ARCHIVES AND RECORDS ADMINISTRATION</AGENCY>
                <DEPDOC>[NARA-NARA-2026-029]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Archives and Records Administration (NARA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We have submitted a request to the Office of Management and Budget (OMB) for approval to reinstate a previously-approved information collection that expired in July 2025. This information collection will be used to connect veterans and Schedule A-eligible applicants with an opportunity for noncompetitive employment. Information will be collected from people who are interested in these opportunities to consider them for the positions and match them with possible jobs. The collection includes approval of a form, NA Form 3102, NARA Employment Interest Questionnaire. We invite you to comment on these information collections.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>OMB must receive written comments on or before August 10, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send any comments and recommendations on the proposed information collection in writing to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         You can find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kristin Phillips, Paperwork Reduction Act Officer, by email at 
                        <E T="03">kristin.phillips@nara.gov</E>
                         or by telephone at 616-254-0405.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Pursuant to the Paperwork Reduction Act of 1995 (Pub. L. 104-13), we invite the public and other Federal agencies to comment on proposed information collections. We published a notice of proposed collection for these information collections on May 8, 2026 (91 FR 25388) and we received 0 comments. We are therefore submitting the described information collections to OMB for approval.</P>
                <P>If you have comments or suggestions, they should address one or more of the following points: (a) whether the proposed information collections are necessary for NARA to properly perform its functions; (b) our estimate of the burden of the proposed information collections and its accuracy; (c) ways we could enhance the quality, utility, and clarity of the information we collect; (d) ways we could minimize the burden on respondents of collecting the information, including through information technology; and (e) whether these collections affect small businesses.</P>
                <P>In this notice, we solicit comments concerning the following information collection:</P>
                <P>
                    <E T="03">Title:</E>
                     Schedule A and Veterans Recruitment Initiative.
                </P>
                <P>
                    <E T="03">OMB number:</E>
                     3095-0075.
                </P>
                <P>
                    <E T="03">Agency form number:</E>
                     NA Form 3102, NARA Employment Interest Questionnaire.
                </P>
                <P>
                    <E T="03">Type of review:</E>
                     Regular.
                </P>
                <P>
                    <E T="03">Affected public:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Estimated number of respondents:</E>
                     300.
                </P>
                <P>
                    <E T="03">Estimated time per response:</E>
                     5 minutes.
                </P>
                <P>
                    <E T="03">Frequency of response:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Estimated total annual burden hours:</E>
                     25 hours.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This recruitment initiative connects people who are veterans or are Schedule A-eligible with non-competitive employment opportunities within our agency. The Special Program Placement Coordinator (SPPC) serves as a liaison between the applicant and NARA managers and supervisors to find viable employment opportunities for applicants.
                </P>
                <P>SPPC has developed a Resume Repository (retained in a spreadsheet) to store resumes of qualified individuals who may meet our hiring needs. The Repository helps our agency find highly motivated veterans and Schedule A candidates who are eager to demonstrate their abilities in the workplace through excepted service positions, which could become permanent positions after trial period requirements have been met.</P>
                <P>We collect the information for the Repository through an online form, NA Form 3102, NARA Employment Interest Questionnaire, which includes the following information for each individual: Applicant name, email address, phone number, U.S. citizenship status, past federal employment, referral source, desired work location, types of positions applicant is interested in (may be multiple areas of interest), and minimum starting grade level.</P>
                <P>We enter the collected information from the questionnaire into the Repository spreadsheet, which managers and supervisors can use to sort and filter by position(s) of interest and/or duty location. We include resumes and cover letters as a link beside each candidate's entry so managers can view them and consider the candidate when looking for an employee. Managers have unlimited access to the Repository information and resumes to select qualified applicants to fill vacancies through a direct, non-competitive hire.</P>
                <P>
                    The Schedule A and veterans recruitment questionnaire link will be listed in our agency's information on the OPM website, in information provided by other agencies and organizations with similar programs, and on various pages of our agency's website at 
                    <E T="03">https://www.archives.gov/.</E>
                     Candidates must be U.S. citizens, eligible veterans, or be eligible under the Schedule A hiring authority.
                </P>
                <SIG>
                    <NAME>Gulam Shakir,</NAME>
                    <TITLE>Executive for Information Services/CIO.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13879 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7515-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="42562"/>
                <AGENCY TYPE="N">NATIONAL CREDIT UNION ADMINISTRATION</AGENCY>
                <SUBJECT>Community Development Revolving Loan Fund</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Credit Union Administration (NCUA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of funding opportunity.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NCUA is issuing this Notice of Funding Opportunity (NOFO) to announce the availability of loan funding for qualifying credit unions through the Community Development Revolving Loan Fund (CDRLF). The CDRLF provides financial support that helps credit unions support the communities in which they operate.</P>
                </SUM>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Table of Contents</HD>
                <FP SOURCE="FP-2">Basic Information</FP>
                <FP SOURCE="FP-2">Eligibility</FP>
                <FP SOURCE="FP-2">Program Description</FP>
                <FP SOURCE="FP-2">Eligible Activities</FP>
                <FP SOURCE="FP-2">Application Contents and Format</FP>
                <FP SOURCE="FP-2">Submission Requirements and Deadlines</FP>
                <FP SOURCE="FP-2">Application Review Information</FP>
                <FP SOURCE="FP-2">Award Notices</FP>
                <FP SOURCE="FP-2">Post-Award Requirements and Administration</FP>
                <FP SOURCE="FP-2">Other Information</FP>
                <HD SOURCE="HD1">Basic Information</HD>
                <P>
                    <E T="03">Funding Opportunity Title:</E>
                     Community Development Revolving Loan Fund (CDRLF) Loan Program.
                </P>
                <P>
                    <E T="03">Announcement Type:</E>
                     Initial Notice of Funding Opportunity (NOFO or Notice).
                </P>
                <P>
                    <E T="03">Funding Opportunity Number:</E>
                     NCUA-CDRLF-2026L.
                </P>
                <P>
                    <E T="03">Assistance Listing Number:</E>
                     44.002.
                </P>
                <P>
                    <E T="03">Funding Details:</E>
                     NCUA is announcing the availability of $13 million in revolving loan funds available for CDRLF loan awards. NCUA may fund, in whole or in part, any, all, or none of the applications submitted in response to this NOFO. All loan awards made under this NOFO are subject to availability of funds and made at NCUA's discretion. Available funds will be revolved as loans are repaid and new awards are made. Individual loans range from $50,000 to $500,000.
                </P>
                <P>
                    <E T="03">Number of Expected Awards Annually:</E>
                     5-15.
                </P>
                <P>
                    <E T="03">Key Dates:</E>
                     This NOFO is effective on the date of publication in the 
                    <E T="04">Federal Register</E>
                    . NCUA accepts applications on a rolling basis. Applicants will be notified of NCUA's decision after the agency's review is completed. The application review process will take approximately 180 calendar days.
                </P>
                <P>
                    <E T="03">Executive Summary:</E>
                     Through the CDRLF NOFO, NCUA will provide financial support in the form of loans to eligible credit unions to modernize, build capacity, or extend outreach to low-income members (as defined in 12 CFR 701.34) and the communities in which they operate.
                </P>
                <P>
                    Agency Contact Information: If you need to contact NCUA regarding the CDRLF loan program, please email 
                    <E T="03">CUREAPPS@NCUA.gov</E>
                     or call (703) 518-6610. Please allow up to 72 business hours for a response.
                </P>
                <HD SOURCE="HD1">Eligibility</HD>
                <P>This NOFO is open to low-income-designated credit unions that meet the eligibility requirements defined in 12 CFR part 705 and further detailed in the bulleted list below.</P>
                <HD SOURCE="HD2">Requirements for a Loan Applicant</HD>
                <P>• Applicants must have a current low-income designation under 12 CFR 701.34 or 12 CFR 741.204. Applicants that are non-federally insured credit unions must have a low-income designation from a state regulator made under appropriate state standards with the concurrence of NCUA. Services to low-income members must include, at a minimum, offering share accounts and loans.</P>
                <P>• Applicants must be a credit union that may be, or has agreed to be, examined by NCUA. See definition of Qualifying Credit Union in 12 CFR 705.2. Each applicant that is a non-federally insured, state-chartered credit union must submit additional application materials and agree to be examined by NCUA. The additional materials are more fully described in 12 CFR 705.7(b)(3). The specific terms and covenants pertaining to the agreement to be examined by NCUA will be provided in the award agreement.</P>
                <P>• Applicants must maintain an active registration with the System for Award Management (SAM) at all times during which they have an active federal award as a recipient or an application under consideration by a federal agency. Additional details on SAM registration are listed in the “SAM section” below.</P>
                <P>• Applicants must have and include a valid and current Employer Identification Number (EIN) issued by the U.S. Internal Revenue Service (IRS). NCUA will not consider an application that does not include a valid and current EIN. Information on how to obtain an EIN may be found on the IRS website.</P>
                <P>• Applicants shall not submit an application on behalf of another organization. This prohibits any application being submitted by a consultant, subsidiary, or parent company of a qualifying credit union on behalf of a qualifying credit union. The qualifying credit union must submit its own application.</P>
                <P>• Applicants must meet the loan award standards established by NCUA, including those pertaining to financial viability, as set forth in the application and defined in 12 CFR 705.7(b) and 705.7(c).</P>
                <P>• Applicants must submit applications that adhere to applicable authorizing statutes, regulations, and administrative and national policy requirements, including Executive Orders and other Presidential directives as detailed in the “Application Contents and Format” section.</P>
                <P>• Consistent with Executive Order 14151 and Executive Order 14173, applicants must not submit comparative statistics or other demographical information on the basis of an individual's or group's race, ethnicity, sex, or national origin. Consistent with Executive Order 14218, applicants will adhere to the Personal Responsibility and Work Opportunity Reconciliation Act of 1996.</P>
                <P>• Applicants must submit applications that meet the review and criteria requirements in the “Application Review Information” section and the submission deadline requirements in the “Submission Requirements and Deadlines” section.</P>
                <P>• Per 12 CFR 705.8, applicants must comply with additional eligibility requirements set forth by NCUA for Emergency Loans, if applicable.</P>
                <HD SOURCE="HD2">Cost Sharing</HD>
                <P>Cost sharing is not required or requested for this funding announcement; if NCUA chooses to require cost sharing or matching funds, it will be announced through a press release and additional guidance.</P>
                <HD SOURCE="HD1">Program Description</HD>
                <P>The purpose of the CDRLF, as fully described in 12 CFR 705.1, is to assist qualifying credit unions with providing basic financial services to their members and to stimulate economic activities in their communities.</P>
                <HD SOURCE="HD1">Eligible Activities</HD>
                <P>Additional details on the eligible activities, performance metrics, and specific ineligible costs can be found in the CDRLF Loan Application Guidelines.</P>
                <P>
                    • 
                    <E T="03">Low-Interest Loan ($500,000 maximum award amount):</E>
                     Eligible credit unions can use loan funds to complete capacity building activities required to grow and meet the unique needs of their members. Eligible project 
                    <PRTPAGE P="42563"/>
                    activities include, but are not limited to, expenses related to:
                </P>
                <P>○ Development of new products or services for members, including new or expanded share draft or credit card programs.</P>
                <P>○ Partnership arrangements with community-based service organizations or government agencies.</P>
                <P>○ Loan programs, including, but not limited to, microbusiness loans, payday loan alternatives, education loans, and real estate loans.</P>
                <P>○ Acquisition, expansion, or improvement of office space or equipment, including branch facilities, ATMs, and electronic banking facilities.</P>
                <P>○ Operational programs.</P>
                <P>
                    • 
                    <E T="03">Emergency Loan ($500,000 maximum award amount):</E>
                     Loans are available to assist qualifying credit unions responding to an unforeseen emergency such as natural disasters, unexpected events outside of the credit union's control, or declared state or national emergencies. Emergency Loan awards may differ in term, interest rate, and allowable activities based on the emergency faced. The agency will announce details for Emergency Loans through NCUA Express messages, social media posts, and updates to our website.
                </P>
                <HD SOURCE="HD2">Citations for Authorizing Statutes and Regulations</HD>
                <P>
                    <E T="03">Authority:</E>
                     12 U.S.C. 1772c-1, 1756, 1757(5)(D), and (7)(I), 1766, 1782, 1784, 1785 and 1786; 42 U.S.C. 9812, 9822, and 9910 (1981).
                </P>
                <P>
                    <E T="03">Regulations:</E>
                     12 CFR part 705 is the governing regulation that sets forth the program requirements for the CDRLF. Additional regulations related to the low-income designation are found at 12 CFR 701.34 and 741.204. For the purposes of this NOFO, an “applicant” is a Qualifying Credit Union that submits a complete application to NCUA under the CDRLF.
                </P>
                <P>
                    NCUA encourages applicants to review the regulations, this NOFO, the Executive Orders mentioned in this NOFO, the CDRLF Loan Program Guidelines, and other program materials for a complete understanding of the program. The CDRLF Loan Program Guidelines include the CDRLF Loan Application Guidelines and the CDRLF Post-Award Guidelines. This NOFO, the CDRLF Loan Program Guidelines, and other program materials can be found on NCUA's website at 
                    <E T="03">https://ncua.gov/support-services/credit-union-resources-expansion/grants-loans/loans.</E>
                </P>
                <HD SOURCE="HD1">Application Contents and Format</HD>
                <P>Pre-applications, letters of intent, or white papers are not required or requested.</P>
                <P>All application materials must be submitted through NCUA's award management system. Instructions for accessing NCUA's award management system and submitting the loan application can be found in the CDRLF Loan Application Guidelines.</P>
                <P>Required application information is presented in the CDRLF Loan Application Guidelines. Each loan application requires a narrative that describes the applicant's proposed use of the CDRLF award to enhance its products or services for its members and how these enhanced products or services will support the membership and the community served by the applicant, a project budget, and metrics used to measure the impact of the project. The application must be certified by a credit union official (such as CEO, Manager, or Board Chairperson) authorized to enter agreements with NCUA on behalf of the credit union.</P>
                <P>Applications that do not adhere to applicable authorizing statutes, regulations, and administrative and national policy requirements, including Executive Orders and other Presidential directives, will be rejected.</P>
                <HD SOURCE="HD1">Submission Requirements and Deadlines</HD>
                <P>All applications must be submitted using NCUA's award management system. NCUA accepts applications on a continuous basis subject to funding availability.</P>
                <P>NCUA may alter submission requirements for Emergency Loans through NCUA Express messages and press releases, as authorized under 12 CFR 705.8. Applications for these urgent projects must comply with the terms stated in the applicable announcement.</P>
                <HD SOURCE="HD2">Unique Entity Identifier and System for Award Management (SAM.gov)</HD>
                <P>Federal regulations require all CDRLF applicants to have an active registration with SAM prior to applying for funding. SAM is a web-based, government-wide application that collects, validates, stores, and disseminates business information about the federal government's trading partners in support of contract awards, grants, and electronic payment processes. Applicants receive a Unique Entity Identifier (UEI) upon registration in SAM and must provide this UEI with their application. Applicants must continue to maintain an active SAM registration with current information while they have active federal awards or applications or plans under consideration by a federal agency.</P>
                <P>
                    SAM users can register or recertify their account by following the instructions for registration (
                    <E T="03">https://sam.gov/content/entity-registration</E>
                    ). There is no charge for either the SAM registration or a recertification.
                </P>
                <P>NCUA does not authorize any exemption from this active SAM registration requirement under 2 CFR 25.110(c) or (d).</P>
                <HD SOURCE="HD2">Submission Instructions</HD>
                <P>
                    Prior to applying, applicants must be registered in NCUA's award management system (
                    <E T="03">https://ncua.gov/support-services/credit-union-resources-expansion/grants-loans</E>
                    ). Applicants will also use that award management system to access the application materials. Applications must be submitted online through that system; applications will not be accepted by mail or email. In the event of systems problems, contact NCUA at 
                    <E T="03">CUREAPPS@ncua.gov.</E>
                </P>
                <HD SOURCE="HD2">Intergovernmental Review</HD>
                <P>The CDRLF loan program is not subject to Executive Order 12372, “Intergovernmental Review of Federal Programs.”</P>
                <HD SOURCE="HD1">Application Review Information</HD>
                <HD SOURCE="HD2">Review Criteria</HD>
                <P>NCUA will generally evaluate applications submitted by qualifying credit unions in accordance with 12 CFR 705.7(c). The merit review is conducted by NCUA personnel, and applications are analyzed based on previous experience with the CDRLF program, recent examinations and supervisory information, and the project proposed in the application.</P>
                <P>Project Objective—The application will be evaluated based on how well the proposed project objectives meet the purpose of the CDRLF program as fully described in 12 CFR 705.1.</P>
                <P>Project Budget—The budget must demonstrate that the applicant clearly understands the expenses required to successfully complete the project. The project budget must support the applicant's plan to implement the project and its ability to make the interest payments and eventually repay the loan.</P>
                <P>
                    Financial Viability and Examination Reports—Exam and supervisory information may be used during the analysis of the application. NCUA may assess a credit union's recent examinations or audit reports if a reviewer deems it necessary. Factors 
                    <PRTPAGE P="42564"/>
                    that will be considered include, but are not limited to, enforcement actions, any ongoing supervisory concerns, supervisory or oversight risks, declining financial position, planned merger activity, and compliance risk. Exams may be used to determine the applicant's financial health and its ability to successfully manage a CDRLF loan. Per 12 CFR 705.7(c)(4), in evaluating a Qualifying Credit Union, NCUA will consider all information provided by NCUA staff or state supervisory authority staff that performed the Qualifying Credit Union's most recent examination.
                </P>
                <HD SOURCE="HD2">Review and Selection Process</HD>
                <P>NCUA will determine the loan award amount as applicable for each application in accordance with the regulations at 12 CFR 705.7 and the evaluation process further explained in the CDRLF Loan Application Guidelines.</P>
                <P>The agency will award funds to applications as noted above on a first-come, first-serve basis as long as funds are available. Final award decisions are made by the Director of the Office of Credit Union Resources and Expansion (CURE).</P>
                <HD SOURCE="HD2">Risk Review</HD>
                <P>NCUA will perform a risk assessment as required by 2 CFR 200.206.</P>
                <HD SOURCE="HD1">Award Notices</HD>
                <P>NCUA will notify all applicants of a tentative funding decision by email to the contacts designated in the application after completion of its review. This notice does not obligate program funds but provides instruction on how the Authorized Credit Union Official must review, electronically certify, sign, and submit the Loan and Security Agreement (Loan Agreement) and Promissory Note to accept the CDRLF award by the provided deadline in the notice of Federal Award. Failure to do so may result in the withdrawal of the loan award from the awardee. NCUA will send a final notice of award once all requirements are completed, and funds will be disbursed to the credit union.</P>
                <P>Applicants that are approved for funding will also receive the CDRLF Post-Award Guidelines. These guidelines include instructions on how to proceed with the post-award activities and submission of performance reports.</P>
                <HD SOURCE="HD1">Post-Award Requirements and Administration</HD>
                <P>The maturity date, interest rate, and repayment requirements will be set forth in the Loan Agreement, Promissory Note, and Amortization Schedule at the time of award.</P>
                <P>
                    The interest rate at which the loan must be repaid is determined by the CDRLF Loan Interest Rate Policy effective at the time of application submission. The CDRLF Loan Interest Rate Policy can be found at 
                    <E T="03">https://ncua.gov/support-services/credit-union-resources-expansion/grants-loans/loans.</E>
                </P>
                <P>
                    <E T="03">Important:</E>
                     As a participating credit union (defined in 12 CFR 705.2), an awardee must maintain a current low-income designation during the performance period of the loan. Other terms and conditions, including administrative and National Policy Requirements, are in the CDRLF Loan Application Guidelines, Promissory Note, and Loan Agreement. Awardees that fail to comply with the loan terms and conditions (including maintaining a current low-income designation) may be subject to immediate repayment of any outstanding balances (12 CFR 705.5(f)).
                </P>
                <HD SOURCE="HD2">Reporting</HD>
                <P>Awardees must follow annual reporting requirements stated in 12 CFR 705.9(b) and submit performance reports as detailed in the CDRLF Loan Post-Award Guidelines.</P>
                <P>All post-award activities are to be completed online using NCUA's award management system.</P>
                <HD SOURCE="HD1">Other Information</HD>
                <P>In addition to funding available under this NOFO, NCUA provides funding to qualifying credit unions through the CDRLF Technical Assistance Grant and Newly Chartered and Urgent Needs Grants. More information can be found in the Grants and Loans section of the agency's website.</P>
                <HD SOURCE="HD2">Paperwork Reduction Act Requirements</HD>
                <P>
                    <E T="03">The collection of information required by this notification of funding opportunity is subject to the Paperwork Reduction Act of 1995, 44 U.S.C. 3501 et seq. The Paperwork Reduction Act of 1995 states that no agency may conduct or sponsor, nor is the respondent required to respond to, an information collection from 10 or more members of the public unless it displays a currently valid Office of Management and Budget (OMB) control number. Pursuant to the Paperwork Reduction Act, the Community Development Revolving Loan Fund Programs have been assigned the following OMB control number: 3133-0138.</E>
                </P>
                <SIG>
                    <FP>By the National Credit Union Administration Board.</FP>
                    <NAME>Ji Kwon,</NAME>
                    <TITLE>Acting Secretary of the Board.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13835 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7535-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL SCIENCE FOUNDATION</AGENCY>
                <SUBJECT>Membership of National Science Foundation's Senior Executive Service Performance Review Board</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Science Foundation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Science Foundation is announcing the members of the Senior Executive Service Performance Review Board.</P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments should be addressed to Chief, Executive Resources, Office of the Chief Human Capital Officer, National Science Foundation, 401 Dulany Street, Alexandria, VA 22314.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Jennifer Munz at the above address or (703) 719-1500.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The membership of the National Science Foundation's Senior Executive Service Performance Review Board is as follows:</P>
                <FP SOURCE="FP-1">Micah Cheatham, Chief Management Officer, Chairperson</FP>
                <FP SOURCE="FP-1">Irina Dolinskaya, Directorate Head, Directorate for Computer and Information Science and Engineering</FP>
                <FP SOURCE="FP-1">Saul Gonzalez, Deputy Directorate Head, Directorate for Mathematical &amp; Physical Sciences</FP>
                <FP SOURCE="FP-1">Theresa Good, Directorate Head, Directorate for Biological Sciences</FP>
                <FP SOURCE="FP-1">Simon Malcomber, Chief Science Officer</FP>
                <FP SOURCE="FP-1">Clyde Richards, Office Head and Chief Information Officer, Office of the Chief Information Officer</FP>
                <FP SOURCE="FP-1">Monya Ruffin, Acting Directorate Head, Directorate for STEM Education</FP>
                <FP SOURCE="FP-1">Angel Williams, General Counsel, Office of General Counsel</FP>
                <P>This announcement of the membership of the National Science Foundation's Senior Executive Service Performance Review Board is made in compliance with 5 U.S.C. 4314(c)(4).</P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Suzanne H. Plimpton,</NAME>
                    <TITLE>Reports Clearance Officer, National Science Foundation.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13887 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7555-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="42565"/>
                <AGENCY TYPE="N">NEIGHBORHOOD REINVESTMENT CORPORATION</AGENCY>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE:</HD>
                    <P>3:00 p.m., Thursday, July 14, 2026.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE:</HD>
                    <P>via ZOOM.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS:</HD>
                    <P>Parts of this meeting will be open to the public. The rest of the meeting will be closed to the public.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P>Annual Board of Directors meeting.</P>
                    <P>The General Counsel of the Corporation has certified that in her opinion, one or more of the exemptions set forth in the Government in the Sunshine Act, 5 U.S.C. 552b(c)(2) permit closure of the following portion(s) of this meeting:</P>
                </PREAMHD>
                <FP SOURCE="FP-1">• Executive (Closed) Session</FP>
                <HD SOURCE="HD1">Agenda</HD>
                <FP SOURCE="FP-2">I. Call to Order</FP>
                <FP SOURCE="FP-2">II. Action Item: Resolution to Elect a Temporary Board Chair</FP>
                <FP SOURCE="FP-2">III. Sunshine Act Approval of Executive (Closed) Session</FP>
                <FP SOURCE="FP-2">IV. Executive Session: CEO Report</FP>
                <FP SOURCE="FP-2">V. Executive Session: CFO Report</FP>
                <FP SOURCE="FP-2">VI. Executive Session: Officer Annual Performance Discussion</FP>
                <FP SOURCE="FP-2">VII. Executive Session: General Counsel Report—Proposed Refinements to Board Governance</FP>
                <FP SOURCE="FP-2">VIII. Action Item: Approval of Meeting Minutes for April 16, 2026 Regular Board Meeting</FP>
                <FP SOURCE="FP-2">IX. Action Item: Board Elections</FP>
                <FP SOURCE="FP-2">X. Action Item: Appointment of Audit Committee</FP>
                <FP SOURCE="FP-2">XI. Action Item: Election of Corporate Officers</FP>
                <FP SOURCE="FP-2">XII. Action Item: Revision to Corporate Bylaws Article II to Require at Least Three Board Meetings Per Year</FP>
                <FP SOURCE="FP-2">XIII. Action Item: Affirming Delegation of Authority to Pay Monthly Health Insurance Premiums</FP>
                <FP SOURCE="FP-2">XIV. Action Item: Approval to Revise Delegation of Authority Policy to Authorize CEO to Spend Consistent with Board-Approved Budget</FP>
                <FP SOURCE="FP-2">XV. Action Item: Approval to Revise Fundraising Policy to Increase Threshold at Which Board Approval is Required to Accept Outside Funds</FP>
                <FP SOURCE="FP-2">XVI. Approval to Increase President &amp; CEO's Grant Making Authority</FP>
                <FP SOURCE="FP-2">XVII. Action Item: Revision to the Delegation of Authority Policy Authorizing the President &amp; CEO to Approve and Execute Master Investment Agreements</FP>
                <FP SOURCE="FP-2">XVIII. Action Item: Acceptance of Internal Audit Review—Corporate Codes of Conduct: Conflict of Interest/Whistleblower Policies, Anon. Reporting Systems</FP>
                <FP SOURCE="FP-2">XIX. Action item: Acceptance of Internal Audit Review—Housing Stability Counseling Program—Quality Control and Compliance</FP>
                <FP SOURCE="FP-2">XX. Action Item: Acceptance of Internal Audit Review—Procure-to-Pay (P2P)</FP>
                <FP SOURCE="FP-2">XXI. Action Item: Acceptance of Internal Audit Review—Procurement Process—Internal Controls</FP>
                <FP SOURCE="FP-2">XXII. Discussion Item: Annual Ethics Review</FP>
                <FP SOURCE="FP-2">XXIII. Management Program Background and Updates</FP>
                <FP SOURCE="FP1-2">a. General Counsel Report</FP>
                <FP SOURCE="FP1-2">b. CIO Report</FP>
                <FP SOURCE="FP1-2">c. CAE Report</FP>
                <FP SOURCE="FP1-2">d. CFO Report</FP>
                <FP SOURCE="FP1-2">i. Financials (through 3/31/26)</FP>
                <FP SOURCE="FP1-2">ii. Single Invoice Approvals $100K and over</FP>
                <FP SOURCE="FP1-2">iii. Vendor Payments $350K and over</FP>
                <FP SOURCE="FP1-2">e. FY25-FY27 SP Scorecard—Q2</FP>
                <FP SOURCE="FP1-2">f. Grants to Capital Corporations</FP>
                <FP SOURCE="FP1-2">g. 2026 Board Calendar</FP>
                <FP SOURCE="FP1-2">h. 2026 Board Agenda Planner</FP>
                <PREAMHD>
                    <HD SOURCE="HED">PORTIONS OPEN TO THE PUBLIC:</HD>
                    <P>Everything except the Executive (Closed) Session.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PORTIONS CLOSED TO THE PUBLIC:</HD>
                    <P>Executive (Closed) Session.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION:</HD>
                    <P>
                        Jenna Sylvester, Paralegal, (202) 568-2560; 
                        <E T="03">jsylvester@nw.org.</E>
                    </P>
                </PREAMHD>
                <SIG>
                    <NAME>Jenna Sylvester,</NAME>
                    <TITLE>Paralegal.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13863 Filed 7-7-26; 11:15 am]</FRDOC>
            <BILCOD>BILLING CODE 7570-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">OFFICE OF PERSONNEL MANAGEMENT</AGENCY>
                <SUBJECT>Submission for Renewal: Questionnaire for National Security Positions, Standard Form 86 (SF 86)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Personnel Management.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>60-Day notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of Personnel Management (OPM), Suitability Executive Agent Programs, is notifying the general public and other federal agencies that OPM proposes to request the Office of Management and Budget (OMB) renew Standard Form 86 (SF 86), Questionnaire for National Security Positions, without change.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before September 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments on the Federal Rulemaking Portal: 
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments. The general policy for comments and other submissions from members of the public is to make these submissions available for public viewing at 
                        <E T="03">http://www.regulations.gov</E>
                         as they are received without change, including any personal identifiers or contact information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Joe Knouff, Director, Suitability Executive Agent Programs, U.S. Office of Personnel Management, P.O. Box 699, Slippery Rock, PA 16057, or by email at 
                        <E T="03">SuitEA@opm.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3506(c)(2)(A)), OPM provides the general public and Federal agencies an opportunity to comment on this proposed renewal of an information collection. This process helps ensure that the collection is necessary for the proper performance of agency functions, minimizes public burden, and enhances the practical utility of the information collected.</P>
                <P>The Questionnaire for National Security Positions, Standard Form 86 (SF 86), is currently used to collect information completed by applicants for, or incumbents of, Federal Government civilian positions, or positions in private entities performing work for the Federal Government under contract. The information collected is used as the basis of information for background investigations to determine whether individuals in national security positions are suitable or fit for employment or retention; fit to perform work on behalf of the Federal Government pursuant to a contract; and eligible for physical and logical access to federally controlled facilities or information systems. For applicants for civilian Federal employment, SF 86 is used only after a conditional offer of employment has been made.</P>
                <P>
                    The National Background Investigation Services (NBIS) electronic application (eApp) is the primary system used to collect this information. The electronic format incorporates branching logic that tailors questions based on an individual's responses, thereby reducing respondent burden by limiting questions to those relevant to the individual's personal history. The eApp system contains the investigative Standard Forms used by Federal applicants and employees to submit information required for personnel background investigations. Because the electronic application uses tailored questions and instructions, the 
                    <PRTPAGE P="42566"/>
                    estimated burden varies depending on the relevance of questions to an individual's personal history.
                </P>
                <P>
                    This information collection is currently approved by OMB, and OPM is seeking renewal without substantive change. OPM received approval in February of 2024 for non-substantive revisions to this collection which was previously approved in November of 2023. Pursuant to the Economic Growth, Regulatory Relief, and Consumer Protection Act (Pub. L. 115-174), security freezes do not restrict access to credit reports for employment, tenant, or background screening purposes; therefore, individuals are no longer required to lift a credit freeze during a background investigation and the instructions within the form were updated accordingly. Additionally, de minimis changes were made in May of 2025 to align with Executive Order 14168, 
                    <E T="03">Defending Women From Gender Ideology Extremism and Restoring Biological Truth to the Federal Government,</E>
                     January 20, 2025. These updates have already been incorporated into the eApp system.
                </P>
                <P>
                    A copy of the proposed information collection and the associated instructions are available at: 
                    <E T="03">https://www.reginfo.gov/public/do/PRAMain.</E>
                     Use the search function to enter either the title of the collection (
                    <E T="03">Questionnaire for National Security Positions</E>
                    ) or the OMB Control Number (3206-0005). OPM is not proposing any revisions to the form at this time. OPM recommends renewal of the form without any proposed changes due to the forthcoming plan to replace the SF 86 with the Personnel Vetting Questionnaire (87 FR 71700 and 88 FR 12703), which is currently approved and in development.
                </P>
                <P>OPM invites comments on:</P>
                <P>1. Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>2. The accuracy of the agency's estimate of the burden of the proposed collection of information;</P>
                <P>3. Ways to enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>4. Ways to minimize the burden of the collection of information on respondents, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.</P>
                <HD SOURCE="HD1">Analysis</HD>
                <P>
                    <E T="03">Agency:</E>
                     Suitability Executive Agent Program, Office of Personnel Management.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Questionnaire for National Security Positions (SF 86).
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3206-0005.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or Households.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     495,924.
                </P>
                <P>
                    <E T="03">Estimated Time Per Respondent:</E>
                     150 minutes.
                </P>
                <P>
                    <E T="03">Total Burden Hours:</E>
                     1,239,810.
                </P>
                <SIG>
                    <FP>Office of Personnel Management.</FP>
                    <NAME>Alexys Stanley,</NAME>
                    <TITLE>Federal Register Liaison.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13868 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6325-66-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[OMB Control No. 3235-0288]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed Collection; Comment Request; Extension: Form 20-F</SUBJECT>
                <FP SOURCE="FP-1">
                    <E T="03">Upon Written Request, Copies Available From:</E>
                     Securities and Exchange Commission, Office of FOIA Services, 100 F Street NE, Washington, DC 20549-2736
                </FP>
                <P>
                    Notice is hereby given that, pursuant to the Paperwork Reduction Act of 1995 (“PRA”) (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the Securities and Exchange Commission (“Commission”) is soliciting comments on the collection of information summarized below. The Commission plans to submit this existing collection of information to the Office of Management and Budget (“OMB”) for extension and approval.
                </P>
                <P>Form 20-F (17 CFR 249.220f) is used by foreign private issuers to register securities pursuant to Section 12 of the Securities Exchange Act of 1934 (“Exchange Act”) and to file annual or transition reports pursuant to Section 13(a) or 15(d) of the Exchange Act. The information collected by Form 20-F is intended to provide investors with material information needed to make informed investment decisions. We estimate that Form 20-F is filed once per year by approximately 1,029 respondents, for a total of approximately 1,029 responses annually. We estimate that respondents incur 660.89 burden hours per Form 20-F response, for a total annual reporting burden of 680,056 hours (660.89 hours per response × 1,029 responses). We estimate that respondents incur $1,194,666.92 cost burden per Form 20-F, for a total annual cost of $1,229,312,261 ($1,194,666.92 cost per response × 1,029 responses).</P>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number.</P>
                <P>
                    <E T="03">Written comments are invited on:</E>
                     (a) whether this proposed collection of information is necessary for the proper performance of the functions of the SEC, including whether the information will have practical utility; (b) the accuracy of the SEC's estimate of the burden imposed by the proposed collection of information, including the validity of the methodology and the assumptions used; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated, electronic collection techniques or other forms of information technology.
                </P>
                <P>
                    Please direct your written comments on this 60-Day Collection Notice to Austin Gerig, Director/Chief Data Officer, Securities and Exchange Commission, c/o Tanya Ruttenberg via email to 
                    <E T="03">PaperworkReductionAct@sec.gov</E>
                     by September 8, 2026.
                </P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13818 Filed 7-8-26; 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-105846; File No. SR-CboeBZX-2026-027]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe BZX Exchange, Inc.; Order Instituting Proceedings To Determine Whether To Approve or Disapprove a Proposed Rule Change To List and Trade Shares of the BondBloxx Private Credit Trust Under BZX Rule 14.11(f), Trust Issued Receipts</SUBJECT>
                <DATE>July 6, 2026.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On April 6, 2026, Cboe BZX Exchange, Inc. (“BZX” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to list and trade shares 
                    <PRTPAGE P="42567"/>
                    (“Shares”) of the BondBloxx Private Credit Trust (“Trust”) under BZX Rule 14.11(f). The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on April 22, 2026.
                    <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. 105274 (Apr. 20, 2026), 91 FR 21527 (“Notice”). The Commission has received no comments regarding the proposed rule change.
                    </P>
                </FTNT>
                <P>
                    On June 1, 2026, 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/>
                     This order institutes proceedings under Section 19(b)(2)(B) of the Act 
                    <SU>6</SU>
                    <FTREF/>
                     to determine whether to disapprove the proposed rule change.
                </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. 105591, 91 FR 33848 (June 4, 2026) (designating July 21, 2026, as the date by which the Commission shall either approve, disapprove, or institute proceedings to determine whether to disapprove the proposed rule change).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">
                    II. Description of the Proposed Rule Change 
                    <SU>7</SU>
                    <FTREF/>
                </HD>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Additional information regarding the Trust and the Shares can be found in the Notice, 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>
                    As described in the Notice, the Exchange proposes to list and trade Shares of the Trust 
                    <SU>8</SU>
                    <FTREF/>
                     under BZX Rule 14.11(f)(4), which governs the listing and trading of Trust Issued Receipts 
                    <SU>9</SU>
                    <FTREF/>
                     on the Exchange. According to the Exchange, the Trust seeks to provide risk-adjusted returns primarily through distributions of current income from the Trust's portfolio.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The Trust has filed an amended registration statement on Form S-1 under the Securities Act of 1933, dated November 20, 2025 (File No. 333-283852) (“Registration Statement”). The description of the Trust and the Shares contained herein is based on the Registration Statement. The Exchange states the Registration Statement for the Trust is not yet effective, and the Trust will not trade on the Exchange until such time that the Registration Statement is effective. 
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21528, n.5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Rule 14.11(f)(4) applies to Trust Issued Receipts that invest in “Investment Shares” or “Financial Instruments.” The term “Investment Shares,” as defined in Rule 14.11(f)(4)(A)(i), means a security (a) that is issued by a trust, partnership, commodity pool or other similar entity that invests in any combination of futures contracts, options on futures contracts, forward contracts, commodities, swaps or high credit quality short-term fixed income securities or other securities; and (b) issued and redeemed daily at net asset value in amounts correlating to the number of receipts created and redeemed in a specified aggregate minimum number. The term “Financial Instruments,” as defined in Rule 14.11(f)(4)(A)(iv), means any combination of investments, including cash; securities; options on securities and indices; futures contracts; options on futures contracts; forward contracts; equity caps, collars and floors; and swap agreements.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         The Exchange states the Trust intends to operate its business so that it is falls outside of the definition of an investment company under the Investment Company Act of 1940 (the “1940 Act”). 
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21528, n.6.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Description of the Trust</HD>
                <P>BondBloxx Investment Management Corporation (“Advisor”) is the advisor to the Trust and is responsible for the overall management of the Trust's business activities. HCG Fund Management LP (“Sub-Advisor”) is responsible for the day-to-day management of the Trust's private credit assets. Brown Brothers Harriman &amp; Co. serves as the administrator, custodian, and the transfer agent. CSC Delaware Trust Company, a Delaware trust company, is the sole trustee of the Trust.</P>
                <P>
                    According to the Exchange, the Trust intends to achieve its investment objective by constructing a diversified portfolio of consumer and small business private credit assets.
                    <SU>11</SU>
                    <FTREF/>
                     The Exchange states the Trust intends to target primarily whole loans that the Advisor believes will offer stable and predictable cash flows.
                    <SU>12</SU>
                    <FTREF/>
                     The Trust generally intends to focus on loans that have short and medium terms (
                    <E T="03">e.g.,</E>
                     less than 60 months) which, through principal amortization, tend to have low duration (
                    <E T="03">e.g.,</E>
                     less than 30 months).
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21528.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Investable Instruments and Trust Liquidity</HD>
                <P>
                    The Exchange states that the permitted investments of the Trust are the following: personal installment loans, small business loans, point of sale loans, and asset backed securities that are backed by such loans (collectively “Private Credit Assets”), investment grade bonds, U.S. Treasuries, shares of certain exchange-traded funds, including certain exchange-traded funds of an affiliated Trust for which the Advisor acts as the investment adviser, that invest in U.S. Treasuries or other short-term, interest bearing assets and cash and cash equivalents.
                    <SU>14</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See id.</E>
                         The Exchange states that, for purposes of this proposal, cash equivalents are short-term instruments with maturities of less than 3 months, specifically including U.S. Government securities, certificates of deposit, bankers' acceptances, repurchase and reverse repurchase agreements, bank time deposits, commercial paper, and money market funds. This definition is consistent with the definition of cash and cash equivalents in Exchange Rule 14.11(i)(4)(C)(iii). 
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21528 n.7.
                    </P>
                </FTNT>
                <P>
                    According to the Exchange, there is limited sell-side liquidity available in the market for Private Credit Assets.
                    <SU>15</SU>
                    <FTREF/>
                     As such, the Advisor is proposing to utilize the following strategy to facilitate redemptions in the Trust:
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21528.
                    </P>
                </FTNT>
                <P>
                    1. The Trust will maintain a portion of the portfolio in cash and cash equivalents (“Liquidity Sleeve”). Under normal circumstances, the Trust expects to hold approximately 20% of the portfolio in these liquid assets.
                    <SU>16</SU>
                    <FTREF/>
                     According to the Exchange, the Advisor expects that it will generally be able to fulfill redemption orders using this position.
                    <SU>17</SU>
                    <FTREF/>
                     The Advisor may also strategically increase the size of the Liquidity Sleeve in order to better facilitate anticipated redemptions by retaining, rather than distributing the paydowns from Private Credit Assets as further described below.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         According to the Exchange, the Trust does not have a prescribed maximum or minimum permissible deviation from the 20% target allocation for the Liquidity Sleeve, and actual allocations may differ from that target, including for extended periods. The 20% figure represents an indicative objective rather than a fixed or binding constraint. The size of the Liquidity Sleeve is determined by the Advisor and Sub-Advisor based on cash flows, the timing and magnitude of subscriptions and redemptions, interest payments, the pace of investment into private credit assets, market conditions, portfolio construction considerations, and the overall size and growth of the Fund. Accordingly, the Liquidity Sleeve may represent a higher or lower percentage of the Fund's net assets over time. 
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21528 n.8.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21528.
                    </P>
                </FTNT>
                <P>
                    2. Under normal circumstances, the remaining 80% of the Trust's holdings will consist of Private Credit Assets. The Exchange states that these assets consist generally of short duration, amortizing loans purchased with a weighted average life ranging from four to thirty-six months. The Trust acquires loans that have been originated and underwritten by fintech lending platforms. According to the Exchange, realized yields will vary over time based on external factors such as market conditions, asset mix, and borrower performance.
                    <SU>18</SU>
                    <FTREF/>
                     Due to the amortizing nature and short duration of the Private Credit Assets, the Trust expects to receive recurring monthly cash flows from interest and principal payments. Monthly cash yield—defined as cash flows received during the month from the Private Credit Asset holdings divided by the opening principal balance of those Private Credit Asset holdings—is expected to range from approximately 5% to 10% but may vary beyond this range due to external factors noted above. Cash flows received may be reinvested or retained at the discretion of the Trust to support portfolio management objectives, including liquidity management and 
                    <PRTPAGE P="42568"/>
                    asset allocation considerations, prior to any distributions to shareholders.
                    <SU>19</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21529.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21528-29.
                    </P>
                </FTNT>
                <P>3. Further, according to the Exchange, in the event that the cash and cash equivalents required to accommodate a series of redemptions or a single large redemption approaches the size of the Trust's Liquidity Sleeve, the Trust may:</P>
                <P>a. Sell Private Credit Assets in the secondary market to raise cash;</P>
                <P>
                    b. Arrange a line of credit or other financing facility with a bank or broker dealer, using the portfolio of Private Credit Assets as collateral.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21529.
                    </P>
                </FTNT>
                <P>
                    The Exchange states these options will likely come at a cost to the Trust or may not be available to the Trust depending on market conditions.
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    4. In the event that items 1-3 above do not provide sufficient cash and cash equivalents to the Liquidity Sleeve to accommodate redemptions in the Trust, the Exchange states redemptions may be suspended until the Trust accumulates enough cash to facilitate additional redemptions, which the Advisor does not expect to last for longer than approximately 2.5 months.
                    <SU>22</SU>
                    <FTREF/>
                     In the event that the Advisor implements a restriction on redemptions, the Shares on the secondary market may trade at deep discount.
                    <SU>23</SU>
                    <FTREF/>
                     According to the Exchange, the discount could potentially serve to prompt investors to buy shares and potentially trigger primary market activity.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    According to the Exchange, the Advisor believes that the liquidity strategy laid out above will be sufficient to address concerns that may arise from the relative illiquidity of the secondary market for selling Private Credit Assets.
                    <SU>25</SU>
                    <FTREF/>
                     Specifically, the Advisor believes that the 20% Liquidity Sleeve (with the flexibility to increase the sleeve during times of potentially high redemptions) will provide the Trust with sufficient liquidity to manage redemptions under the vast majority of market conditions.
                    <SU>26</SU>
                    <FTREF/>
                     Additionally, because the Trust will target shorter duration loans that are underwritten to generate cash payments of interest and principal amortization to achieve its investment objective, even in the event that the Trust's Liquidity Sleeve is exhausted, it is expected to be replenished by the cash payments generated by the Private Credit Assets.
                    <SU>27</SU>
                    <FTREF/>
                     In the event that the cash generated by the Private Credit Assets is insufficient to satisfy incoming redemptions the Trust would then have the ability to facilitate additional redemptions by selling certain of the Private Credit Assets and/or using the Private Credit Assets as collateral for a cash loan from a bank or broker dealer.
                    <SU>28</SU>
                    <FTREF/>
                     According to the Exchange, if necessary, the Trust would temporarily suspend redemptions.
                    <SU>29</SU>
                    <FTREF/>
                     However, the Exchange states the Advisor does not expect such a suspension to last for longer than approximately 2.5 months because of the cash expected to be generated by the Private Credit Assets.
                    <SU>30</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    In addition to the specific liquidity strategy described above, the Exchange states that the small size of loans sourced through fintech lending platforms will enable the Trust to hold a portfolio that is diversified by sector, source, vintage, count and geography, which will help to manage idiosyncratic risk and provide a diverse universe of lenders.
                    <SU>31</SU>
                    <FTREF/>
                     The Exchange states the small loan size means that the Trust will need to hold a significant number of Private Credit Assets, further providing diversity and minimizing the risk that any single Private Credit Assets would have on the portfolio.
                    <SU>32</SU>
                    <FTREF/>
                     Finally, the Exchange states the Advisor believes that the cash yields and short duration through regular principal amortization will, in addition to enhancing the liquidity of the Trust, help manage volatility of returns.
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Availability of Information</HD>
                <P>
                    According to the Exchange, pricing information will be available on the Advisor's website on a daily basis including: (a) the prior business day's net asset value (“NAV”) per Share; (b) the prior business day's BZX Official Closing Price; (c) calculation of the premium or discount of such BZX Official Closing Price against such NAV per Share; (d) a table showing the number of days the Shares traded at a premium or discount; (e) a line graph showing the premium or discount of the Shares; (f) the Trust's median bid-ask spread; and (g) historical distribution data. The NAV per Share will be calculated by the Administrator once a day and will be disseminated daily to all market participants at the same time.
                    <SU>34</SU>
                    <FTREF/>
                     The Trust's website will publish, on a daily basis, quantitative information regarding the Trust's holdings, including the platform, outstanding principal amount or receivable principal, market value, and percentage weight for each asset or, in the case of whole loans, for each origination vintage. In addition, certain portfolio-level characteristics, including sector allocations, asset type allocations, and credit risk information, will be published at least on a quarterly basis. The aforementioned information will be published as of the close of business and available on the Advisor's website at 
                    <E T="03">www.bondbloxxetf.com.</E>
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         NAV means the total assets of the Trust including, but not limited to, all cash and cash equivalents and private credit assets, less any liabilities, divided by the total number of Shares outstanding. The Trust's NAV is determined as the close of regular trading on the Exchange (normally, 4:00 p.m. Eastern Time). The Advisor has delegated to the Administrator the responsibility of computing the Trust's NAV and NAV per Share. 
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21529 n.11.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21529.
                    </P>
                </FTNT>
                <P>
                    According to the Exchange, the Trust generally values its assets using market quotations when they are readily available.
                    <SU>36</SU>
                    <FTREF/>
                     However, according to the Exchange, whole loans and asset backed securities that the Trust may hold may not have readily available market quotations.
                    <SU>37</SU>
                    <FTREF/>
                     In accordance with the Advisor's valuation policies and procedures, the Sub-Advisor will fair value the Trust's private credit assets based on a discounted cash flow (“DCF”) analysis of the loan portfolio's expected future net cash flows over the lifetime of the loan, discounted by the expected return.
                    <SU>38</SU>
                    <FTREF/>
                     Further, in accordance with the valuation policy and procedures, an independent third-party pricing service will provide the inputs for the DCF model, including daily loan tapes (
                    <E T="03">e.g.,</E>
                     loan balances, payment history, interest rates, and FICO scores) along with forward outlook on the portfolio (
                    <E T="03">e.g.,</E>
                     loss expectation).
                    <SU>39</SU>
                    <FTREF/>
                     Additionally, the model may incorporate any publicly available information such as pricing from recent deals or information specific to the Fintech lending platform.
                    <SU>40</SU>
                    <FTREF/>
                     The model will be updated for daily changes to reflect any new information regarding the borrower or loan.
                    <SU>41</SU>
                    <FTREF/>
                     Further, daily cash balances will reflect ending account balances per the Trust's bank account; interest receivable will reflect accrued interest balances for the loan 
                    <PRTPAGE P="42569"/>
                    portfolio per the loan servicer's statement; and prepaid and other assets will reflect ending accrued balances per the general ledger.
                    <SU>42</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21529-30.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, 91 FR at 21530. According to the Exchange, the difference between the calculated net present value and carrying value of the loan portfolio reflects the valuation adjustment that will be updated daily. 
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    According to the Exchange, the Sub-Advisor will review for reasonableness the fair values of the Private Credit Assets provided by the independent third-party pricing services prior to the Sub-Advisor finalizing the daily NAV.
                    <SU>43</SU>
                    <FTREF/>
                     Third-party pricing service providers will be selected based on their experience with similar assets, their demonstrated expertise in fintech, their clearly articulated valuation methodologies and sophistication of modeling capabilities, their independence and objectivity and the quality of their deliverables, their reputation in the industry, and the Advisor's or Sub-Advisor's experience working with the pricing service provider, or other similar pricing service providers, with other vehicles.
                    <SU>44</SU>
                    <FTREF/>
                     Further, the Exchange states that, to the extent that there are material changes in the selection criteria of the third-party pricing service provider or the inputs used or the methodology applied in valuing the Trust's private credit assets, the Trust will notify investors via a prospectus supplement, current report on Form 8-K or annual or quarterly reports, as applicable.
                    <SU>45</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         
                        <E T="03">See id.</E>
                         According to the Exchange, “fair value calculations will involve significant professional judgment in the application of both observable and unobservable attributes, and as a result, the calculated NAV of the Trust's assets may differ from their actual realizable value or future fair value.” 
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    Quotation and last-sale information regarding the Shares will be disseminated through the facilities of the Consolidated Tape Association. Pricing information regarding cash equivalents in which the Trust will invest will be generally available through nationally recognized data services providers, such as Reuters and Bloomberg, through subscription agreements.
                    <SU>46</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    The Exchange states the Intraday Indicative Value (“IIV”) will be updated during Regular Trading Hours to reflect changes in the value of the Trust's holdings during the trading day.
                    <SU>47</SU>
                    <FTREF/>
                     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.
                    <SU>48</SU>
                    <FTREF/>
                     The IIV will be updated every 15 seconds, as calculated by the Exchange or a third-party financial data provider during the Exchange's Regular Trading Hours (9:30 a.m. to 4:00 p.m. Eastern time).
                    <SU>49</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Proceedings To Determine Whether To Approve or Disapprove SR-CboeBZX-2026-027 and Grounds for Disapproval Under Consideration</HD>
                <P>
                    The Commission is instituting proceedings pursuant to Section 19(b)(2)(B) of the Act 
                    <SU>50</SU>
                    <FTREF/>
                     to determine whether the proposed rule change should be approved or disapproved. Institution of such proceedings is appropriate at this time in view of the legal and policy issues raised by the proposed rule change. Institution of proceedings does not indicate that the Commission has reached any conclusions with respect to any of the issues involved. Rather, as described below, the Commission seeks and encourages interested persons to provide comments on the proposed rule change.
                </P>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         15 U.S.C. 78s(b)(2)(B).
                    </P>
                </FTNT>
                <P>
                    Pursuant to Section 19(b)(2)(B) of the Act,
                    <SU>51</SU>
                    <FTREF/>
                     the Commission is providing notice of the grounds for disapproval under consideration. The Commission is instituting proceedings to allow for additional analysis of the proposal's consistency with Section 6(b)(5) of the Act, which requires, among other things, that the rules of a national securities exchange be “designed to prevent fraudulent and manipulative acts and practices, to promote just and equitable principles of trade,” and “to protect investors and the public interest.” 
                    <SU>52</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>The Commission asks that commenters address the sufficiency of the Exchange's statements in support of the proposal, which are set forth in the Notice, in addition to any other comments they may wish to submit about the proposed rule change. In particular, the Commission seeks comment on the following questions and asks commenters to submit data where appropriate to support their views:</P>
                <P>1. What are commenters' views generally with respect to the liquidity and transparency of the markets for Private Credit Assets? What sources of reliable pricing information (both intraday and end-of-day) are available for the Private Credit Assets? Are such sources of reliable pricing information generally available to investors? Do the answers to these questions depend upon the type of Private Credit Asset?</P>
                <P>
                    2. What are commenters' views on whether the proposal would maintain alignment between intraday trading prices of the Shares and the contemporaneous value of the underlying portfolio? Will the proposed allocation of the Trust's holdings, including the liquidity strategy described by the Exchange,
                    <SU>53</SU>
                    <FTREF/>
                     facilitate alignment of the secondary market prices of the Shares with the value of the Trust's underlying portfolio? Why or why not? Will authorized participants and market makers have sufficient information to value the Trust's underlying portfolio and facilitate creation/redemption or trading in the Shares, respectively? Why or why not?
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         
                        <E T="03">See supra</E>
                         notes 16-30 and accompanying text.
                    </P>
                </FTNT>
                <P>3. Given the nature of the underlying assets held by the Trust, what are commenters' views on whether the proposed Trust and Shares would be susceptible to manipulation? What are commenters' views generally on whether the Exchange's proposal is designed to prevent fraudulent and manipulative acts and practices?</P>
                <HD SOURCE="HD1">IV. Procedure: Request for Written Comments</HD>
                <P>
                    The Commission requests that interested persons provide written submissions of their views, data, and arguments with respect to the issues identified above, as well as any other concerns they may have with the proposal. In particular, the Commission invites the written views of interested persons concerning whether the proposal is consistent with Section 6(b)(5) or any other provision of the Act, and the rules and regulations thereunder. Although there do not appear to be any issues relevant to approval or disapproval that would be facilitated by an oral presentation of views, data, and arguments, the Commission will consider, pursuant to Rule 19b-4, any request for an opportunity to make an oral presentation.
                    <SU>54</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         Section 19(b)(2) of the Act, as amended by the Securities Acts Amendments of 1975, Public Law 94-29 (June 4, 1975), grants the Commission flexibility to determine what type of proceeding—either oral or notice and opportunity for written comments—is appropriate for consideration of a particular proposal by a self-regulatory organization. 
                        <E T="03">See</E>
                         Securities Acts Amendments of 1975, Senate Comm. on Banking, Housing &amp; Urban Affairs, S. Rep. No. 75, 94th Cong., 1st Sess. 30 (1975).
                    </P>
                </FTNT>
                <P>
                    Interested persons are invited to submit written data, views, and arguments regarding whether the proposed rule change should be approved or disapproved by July 30, 2026. Any person who wishes to file a rebuttal to any other person's 
                    <PRTPAGE P="42570"/>
                    submission must file that rebuttal by August 13, 2026.
                </P>
                <P>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-2026-027 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-2026-027. 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 filing 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-2026-027 and should be submitted on or before July 30, 2026. Rebuttal comments should be submitted by August 13, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>55</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>55</SU>
                             17 CFR 200.30-3(a)(57).
                        </P>
                    </FTNT>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13829 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[OMB Control No. 3235-0743]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed Collection; Comment Request; Extension: Rule 15b9-1</SUBJECT>
                <FP SOURCE="FP-1">
                    <E T="03">Upon Written Request, Copies Available From:</E>
                     Securities and Exchange Commission, Office of FOIA Services, 100 F Street NE, Washington, DC 20549-2736
                </FP>
                <P>
                    Notice is hereby given that, pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ) (“PRA”), the Securities and Exchange Commission (“SEC” or “Commission”) is soliciting comments on the proposed collection of information provided for in Rule 15b9-1 (17 CFR 240.15b9-1), under the Securities Exchange Act of 1934 (“Act”) (15 U.S.C. 78a 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <P>
                    Section 15(b)(8) of the Act requires any broker or dealer registered with the Commission to become a member of a registered national securities association (“Association”) unless the broker or dealer effects transactions in securities solely on an exchange of which it is a member. This statutory provision sets forth a complementary self-regulatory organization (“SRO”) oversight structure pursuant to which exchange SROs historically have overseen their own exchanges and The Financial Industry Regulatory Authority, Inc. (“FINRA”) (the only Association currently) historically has overseen cross-exchange and off-exchange securities trading activity.
                    <SU>1</SU>
                    <FTREF/>
                     Section 15(b)(9) of the Act provides the Commission with authority to exempt any broker or dealer from Section 15(b)(8), if that exemption is consistent with the public interest and the protection of investors.
                    <SU>2</SU>
                    <FTREF/>
                     The Commission adopted amendments to Rule 15b9-1 
                    <SU>3</SU>
                    <FTREF/>
                     that require a broker or dealer to join an Association if it effects transactions in securities elsewhere than on an exchange to which it belongs as a member, unless it can rely upon one of the amended rule's narrow, contemporary-market-appropriate exceptions from Section 15(b)(8).
                    <SU>4</SU>
                    <FTREF/>
                     Conversely, a broker or dealer would not need to become a member of an Association if it effects securities transactions only on an exchange of which it is a member.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78
                        <E T="03">o</E>
                        (b)(8).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         15 U.S.C. 78o(b)(9).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 240.15b9-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Exchange Act Release No. 98202, (Aug. 23, 2023), 88 FR 61850 (Sep. 7, 2023) (“Adopting Release”); 
                        <E T="03">see also,</E>
                         Exchange Act Release No. 95388 (Jul. 29, 2022), 87 FR 49930 (Aug. 12, 2022) (“Re-Proposal”).
                    </P>
                </FTNT>
                <P>Specifically, Rule 15b9-1, as amended, permits an exemption from Association membership only where a broker or dealer that does not carry customer accounts effects securities transactions otherwise than on a national securities exchange of which it is a member that: (1) result solely from orders that are routed by a national securities exchange of which the broker or dealer is a member to comply with Rule 611 of Regulation NMS or the Options Order Protection and Locked/Crossed Market Plan; or (2) are solely for the purpose of executing the stock leg of a stock-option order (“stock-option order exemption”).</P>
                <P>For purposes of relying on the stock-option order exemption provided by Rule 15b9-1(c)(2), a broker or dealer must establish, maintain and enforce written policies and procedures reasonably designed to ensure and demonstrate that such transactions are solely for the purpose of executing the stock leg of a stock-option order. The broker or dealer is required to preserve a copy of its policies and procedures in a manner consistent with 17 CFR 240.17a-4 until three years after the date the policies and procedures are replaced with updated policies and procedures. These requirements associated with the stock-option order exemption constitute “collection of information requirements” within the meaning of the PRA.</P>
                <P>The collection of information is designed to provide the Commission with enhanced oversight capabilities, consistent with the public interest and protection of investors, by requiring written policies and procedures in connection with the stock-option exemption in paragraph (c)(2) of the amended rule. This requirement helps facilitate exchange SRO supervision of brokers and dealers relying on the stock-option order exemption by providing an efficient and effective way for the relevant options exchange to assess its members' compliance with the terms of the exemption, as set forth in amended Rule 15b9-1.</P>
                <P>
                    The Commission estimates that the total initial reporting burden for those broker-dealers that may rely upon the stock-option order exemption provided for under Rule 15b9-1 would be approximately 8.01 hours per year (annualized over a three-year period) and the total ongoing reporting burden would be approximately 144 hours per year. The Commission estimates that 3 non-FINRA brokers or dealers would rely on the stock-option order exemption.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The Commission cannot discern whether the 3 non-FINRA brokers or dealers rely on the stock-option order exemption newly or on an ongoing basis. As such, the Commission sets forth herein both estimated initial and ongoing reporting burdens.
                    </P>
                </FTNT>
                <P>
                    The Commission estimates that it would take a broker or dealer approximately 8 hours to establish written policies and procedures as required under Rule 15b9-1.
                    <FTREF/>
                    <SU>6</SU>
                     Annualized over a three-year period, 
                    <PRTPAGE P="42571"/>
                    this amounts to an initial burden of approximately 2.67 hours per broker or dealer, per year 
                    <SU>7</SU>
                    <FTREF/>
                     and an aggregate, initial burden of approximately 8.01 hours per year.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         This figure is based on the following: (Compliance Manager at 5 hours) + (Compliance Attorney at 2.5 hours) + (Director of Compliance at 0.5 hour) = 8 burden hours per broker or dealer.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         This figure is based on the following: (8 burden hours per broker or dealer)/(3 years) = 2.67 initial burden hours per broker or dealer, per year.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         This figure is based on the following: (2.67 burden hours per broker or dealer) × (3 brokers and dealers) = 8.01 aggregate initial burden hours per year.
                    </P>
                </FTNT>
                <P>
                    The Commission estimates that the ongoing burden of maintaining and enforcing such policies and procedures, and ensuring that such policies and procedures are reasonably designed to ensure and demonstrate that such transactions are solely for the purpose of executing the stock leg of a stock-option order, would be approximately 48 hours for each broker or dealer per year.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         This figure is based on the following: (Compliance Manager at 30 hours) + (Compliance Attorney at 12 hours) + (Director of Compliance at 6 hours) = 48 burden hours per broker or dealer. In estimating these burden hours, the Commission also examined the estimated initial and ongoing burden hours imposed on registered security-based swap dealers under Regulation SBSR—Reporting and Dissemination of Security-Based Swap Information. 
                        <E T="03">See</E>
                         Exchange Act Release No. 74244 (Feb. 11, 2015), 80 FR 14564, 14683 (Mar. 19, 2015) (“Regulation SBSR”). Regulation SBSR requires registered security-based swap dealers to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure compliance with any security-based swap transaction reporting obligations. 
                        <E T="03">Id.</E>
                         The estimated initial and ongoing compliance burden on registered security-based swap dealers under Regulation SBSR were 216 burden hours and 120 burden hours, respectively. 
                        <E T="03">Id.</E>
                         The policies and procedures under Rule 15b9-1 are much more limited in nature.
                    </P>
                </FTNT>
                <P>
                    Based on an estimated annual burden of 48 hours per broker or dealer, the Commission estimates that the aggregate, ongoing burden to maintain and enforce written policies and procedures as required under Rule 15b9-1 would be 144 hours per year.
                    <SU>10</SU>
                    <FTREF/>
                     As a result, the total industry burden, including the initial burden and the ongoing burden, would be approximately 152.01 hours per year.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         This figure is based on the following: (48 burden hours per broker or dealer) × (3 non-FINRA brokers and dealers) = 144 aggregate, ongoing burden hours per year.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         This figure is based on the following: (8.01 aggregate, initial burden hours) + (144 aggregate, ongoing burden hours) = 152.01 total burden hours per year.
                    </P>
                </FTNT>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB Control Number.</P>
                <P>
                    <E T="03">Written comments are invited on:</E>
                     (a) whether this proposed collection of information is necessary for the proper performance of the functions of the SEC, including whether the information will have practical utility; (b) the accuracy of the SEC's estimate of the burden imposed by the proposed collection of information, including the validity of the methodology and the assumptions used; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated, electronic collection techniques or other forms of information technology.
                </P>
                <P>
                    Please direct your written comments on this 60-Day Collection Notice to Austin Gerig, Director/Chief Data Officer, Securities and Exchange Commission, c/o Tanya Ruttenberg via email to 
                    <E T="03">PaperworkReductionAct@sec.gov</E>
                     by September 8, 2026.
                </P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13816 Filed 7-8-26; 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-105849; File No. SR-FICC-2026-007]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Fixed Income Clearing Corporation; Notice of Filing of Proposed Rule Change To Modify the GSD Rules To Adopt a U.S. Treasury Clearing Trade Submission Requirement</SUBJECT>
                <DATE>July 6, 2026.</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 June 24, 2026, Fixed Income Clearing Corporation (“FICC”) 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 primarily by the clearing agency. 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. Clearing Agency's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    The proposed rule change consists of modifications to FICC's Government Securities Division (“GSD”) Rulebook (“Rules”) 
                    <SU>3</SU>
                    <FTREF/>
                     to (1) adopt a requirement that each Netting Member submits all eligible secondary market transactions, both for repurchase agreements and certain categories of cash transactions, to which it is a counterparty to FICC for clearance and settlement; (2) adopt provisions to monitor and enforce the trade submission requirement; and (3) make other revisions to the Rules to clarify, conform and enhance the disclosures of the Rules, as described below.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Terms not defined herein are defined in the Rules, 
                        <E T="03">available at www.dtcc.com/~/media/Files/Downloads/legal/rules/ficc_gov_rules.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    These proposed rule changes are primarily designed to comply with the requirements of Rule 17ad-22(e)(18)(iv)(A) and (B) under the Act, as described below.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.17ad-22(e)(18)(iv)(A) and (B). 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 99149 (Dec. 13, 2023), 89 FR 2714 (Jan. 16, 2024) (“Adopting Release”, and the rules adopted therein referred to herein as “Treasury Clearing Rules”).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Clearing Agency's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, the clearing agency 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 clearing agency 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) Clearing Agency's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <HD SOURCE="HD3">Executive Summary</HD>
                <P>
                    On December 13, 2023, the Commission adopted amendments to the covered clearing agency standards that apply to covered clearing agencies that clear transactions in U.S. Treasury securities, including FICC.
                    <SU>5</SU>
                    <FTREF/>
                     These amendments require, among other things, that FICC establish objective, risk-based, and publicly disclosed criteria for participation that (i) require FICC's Netting Members submit for clearance and settlement all of the eligible secondary market transactions to which they are a counterparty; and (ii) identify and monitor Netting Members' submission of eligible secondary market transactions to which they are a counterparty, including how FICC would address a failure to submit transactions in accordance with this requirement.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    Therefore, under the Treasury Clearing Rules, FICC must require its Netting Members, as direct participants, 
                    <PRTPAGE P="42572"/>
                    to submit all eligible secondary market transactions to which they are a counterparty to it for central clearing. FICC is also obligated to adopt provisions that would facilitate its monitoring of Netting Members' compliance with the trade submission requirement and how it would address a Member's failure to comply. As described below, the proposed rules are designed to comply with those requirements.
                </P>
                <P>
                    First, the proposed changes would adopt an ongoing membership requirement that all Netting Members submit to FICC for clearance and settlement eligible secondary market transactions to which they are a party in a new GSD Rule 5. The proposed rules would adopt a definition of Eligible Secondary Market Transactions by reference to the Treasury Clearing Rules 
                    <SU>7</SU>
                    <FTREF/>
                     to ensure that FICC's trade submission requirement is consistent with such regulations and with the requirements being adopted by other U.S. Treasury clearing agencies.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">Supra</E>
                         note 4. 
                        <E T="03">See also</E>
                         17 CFR 240.17ad-22(a).
                    </P>
                </FTNT>
                <P>Second, the proposed changes would adopt provisions to enable FICC to identify and monitor Netting Members' ongoing compliance with the proposed trade submission requirement. These provisions would include affirmative obligations of Netting Members to notify FICC of non-compliance with this requirement. These provisions would also extend FICC's existing authority to request information or review a Netting Member's books and records to its monitoring and verification, as needed, of such compliance. Therefore, FICC's proposal would rely on Member self-reporting and its existing authority to request information and examine a Netting Member's books and records to fulfill its requirement to identify and monitor Netting Members' compliance with the requirement.</P>
                <P>The proposed rule changes would also adopt disciplinary measures FICC would take if a Netting Member fails to meet its obligations under the new rules, which would include a fine and notifications to applicable regulatory authorities. The fine would be incorporated into the GSD Fine Schedule and would be waived for any Netting Member that self-reports non-compliance and remediates such non-compliance within a specified timeframe.</P>
                <P>Finally, the proposed rule changes would include non-substantive revisions to re-organize, clarify and conform the GSD Rules, as described below.</P>
                <HD SOURCE="HD3">Background</HD>
                <P>
                    FICC, through GSD, serves as a central counterparty and provider of clearance and settlement services for the U.S. government securities markets. GSD's central counterparty services are available directly to entities that are approved to be Netting Members and indirectly to other market participants through its indirect access models—the Sponsored Service or Agent Clearing Service.
                    <SU>8</SU>
                    <FTREF/>
                     FICC's direct participants include brokers, dealers, inter-dealer brokers, futures commission merchants, government securities issuers, insurance companies, registered clearing agencies, registered investment companies and both U.S. and non-U.S. banks. Currently, other market participants, including investment funds, pension plans and other buy-side institutions, generally access GSD's central counterparty services through one of its indirect access models.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Rule 2 (Members) (providing that FICC shall make its services available to entities that are approved to be Members of GSD); Rule 3A (Sponsoring Members and Sponsored Members) (describing the “Sponsored Service”); and Rule 8 (Agent Clearing Service), 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>
                    Through GSD, FICC provides real-time trade matching, clearing, risk management and netting for cash purchases and sales of eligible securities, as well as repurchase and reverse repurchase transactions involving eligible securities (“Repo Transactions”). Eligible securities include securities issued by the U.S. Treasury Department (“U.S. Treasury Securities”) and securities issued or guaranteed by U.S. government agencies and government sponsored enterprises.
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         definition of “Eligible Securities” in Rule 1, 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>
                    In its role as central counterparty, FICC novates eligible transactions that are submitted to it for clearance and settlement. Novation is defined in the Rules as the termination of deliver, receive, and related payment obligations between pre-novation counterparties and the replacement of such obligations with identical obligations to and from FICC, pursuant to the provisions of the Rules, and generally occurs at the time a submitted transaction is compared by FICC.
                    <SU>10</SU>
                    <FTREF/>
                     As recognized by the Commission in the Adopting Release, by “novating transactions (that is, becoming the counterparty to both sides of a transaction), [FICC] addresses concerns about counterparty risk by substituting its own creditworthiness and liquidity for the creditworthiness and liquidity of the counterparties.” 
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         definition of “Novation” in Rule 1, 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">Supra</E>
                         note 4, at 8-9.
                    </P>
                </FTNT>
                <P>
                    The Adopting Release identifies the important operational, risk management and other benefits of central clearing, which include the reduction in counterparty credit risk through novation of trades by the central counterparty, centralized default management, and efficiencies provided by multilateral netting.
                    <SU>12</SU>
                    <FTREF/>
                     The efficacy of FICC's own risk management framework is critical to its ability to provide these benefits to the market it serves.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Supra</E>
                         note 4, at 14-17.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Description of Proposed Rule Changes</HD>
                <HD SOURCE="HD3">1. Adopt Trade Submission Requirement and Define Scope of Requirement </HD>
                <P>
                    The proposed rule changes would adopt an ongoing membership obligation that each Netting Member submit to FICC, or to another clearing agency that provides central counterparty services for transactions in U.S. Treasury Securities, for clearance and settlement all “Eligible Secondary Market Transactions” to which such Netting Member (or a part of the Netting Member, as the Commission may provide through interpretive guidance or exemptive relief) is a counterparty. This requirement would be added to a new Rule 5 
                    <SU>13</SU>
                    <FTREF/>
                     and would be adopted to comply with both the amendments to Rule 17ad-22(e)(18)(iv)(A) under the Act,
                    <SU>14</SU>
                    <FTREF/>
                     and with any future guidance or rulemaking of the Commission with respect to the scope of that rule.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         The rules currently in Rule 5, describing the Comparison System, would be moved to a new Rule 6. References to current Rule 5 would be updated throughout the Rules to reflect this change. 
                        <E T="03">Supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         17 CFR 240.17ad-22(e)(18)(iv)(A).
                    </P>
                </FTNT>
                <P>Rule 5 would also provide that Netting Members are permitted, but not required, to submit to FICC transactions that are outside the scope of the new trade submission requirement.</P>
                <HD SOURCE="HD3">a. Scope of Trade Submission Requirement</HD>
                <P>
                    The proposed rule changes would specify the scope of the trade submission requirement by adopting the definition of “Eligible Secondary Market Transactions” in the Treasury Clearing Rules.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         17 CFR 240.17ad-22(a).
                    </P>
                </FTNT>
                <P>
                    The Commission's definition of Eligible Secondary Market Transactions generally includes secondary market transactions in U.S. Treasury Securities where the transaction is of a type that is accepted by FICC for clearance and settlement and, subject to specified exceptions and exemptions, is one of three specified types of transactions: (i) repurchase transactions in U.S. Treasury 
                    <PRTPAGE P="42573"/>
                    Securities entered into by the Netting Member; (ii) cash transactions on U.S. Treasury Securities entered into by the Netting Member if the Netting Member is an Inter-Dealer Broker; and (iii) all cash transactions on U.S. Treasury Securities entered into by the Netting Member with a broker-dealer, government securities dealer, or government securities broker.
                    <SU>16</SU>
                    <FTREF/>
                     The Commission's definition excludes certain transactions entered into with certain specified counterparties, including central banks and sovereign entities.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    The proposed rule changes would adopt a definition of the term, Eligible Secondary Market Transactions, into Rule 1 by reference to the definition set forth in Rule 17ad-22(a) under the Act, which would ensure consistency with the Act.
                    <SU>17</SU>
                    <FTREF/>
                     The proposed definition further defines Eligible Secondary Market Transaction to include any interpretation of that term that may be issued by the Commission and its staff from time to time and would exclude any transactions that are exempted or excluded from the trade submission requirement under Rule 17ad-22(a) under the Act by the Commission or its staff. Similar to the language that would be added to the proposed Rule 5 (discussed above), this proposed language would permit the scope of the trade submission requirement to remain consistent with the binding definition of such term by preemptively incorporating any future guidance, interpretation or exemption published by Commission or its staff related to that definition.
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>FICC is also proposing to clarify language in the Rules to make clear that a bank and its branches must all apply under the same membership, as one Bank Netting Member. This proposed revision would clarify that a branch and its parent bank are considered the same legal entity under the GSD Rules and not separate affiliates. The proposed changes would remove reference to a bank applying for membership through its branch or agency from various places in Rules 2A and 3, including (1) updating eligibility to be a Bank Netting Member to remove the ability in Section 3(a)(i) of Rule 2A of a non-U.S. bank to participate through a U.S. branch as an alternative to meeting the qualifications applicable to a Foreign Person and including in this Section 3(a)(i) clarifying language regarding FICC's position on Bank Netting Members; (2) updating the descriptions of financial requirements applicable to both Bank Netting Members established or chartered under the laws of a non-U.S. jurisdiction and other Foreign Persons that are banks to remove reference to an application for membership through a U.S. branch in Sections 4(b)(ii)(A)(2) and (E)(2) of Rule 2A; and (3) removing reference to a bank's branch in the description of the annual attestation that must be provided by non-U.S. bank Netting Members in Section 2 of Rule 3.</P>
                <HD SOURCE="HD3">b. Remove Existing Trade Submission Requirements</HD>
                <P>In connection with adopting this trade submission requirement, FICC would remove the existing trade submission requirements from the GSD Rules. These requirements are currently set forth in Section 1 of Rule 5 (to be re-numbered Rule 6), Section 3 of Rule 11, Rule 15, and Section 2 of Rule 18.</P>
                <P>Section 1 of Rule 5 requires that Members of the Comparison System submit to FICC for comparison trade data on all trades that are of the type processed by FICC. Section 3 of Rule 11 requires Netting Members to submit data on all of that Netting Member's or the Netting Member's Executing Firm Customers' trades other than Repo Transactions (i) with other Netting Members (or their Executing Firm Customers) that are eligible for netting and (ii) executed by a Covered Affiliate (as defined in Rule 1) that meet certain criteria. Section 2 of Rule 18 includes an identical trade submission obligation with respect to trade data on Netting Members' Repo Transactions. Both Rules exclude certain trades from the submission requirement, including trades executed between Netting Members and their Affiliates (defined in these Rules as “Affiliate Trades”). Rule 15 requires that Inter-Dealer Broker Netting Members submit to FICC trade data regarding their brokered activity, other than Repo Transactions, upon FICC's request.</P>
                <P>FICC is proposing to remove these provisions from the Rules. The activity that would be required to be submitted to FICC pursuant to the trade submission requirement proposed to be added to new Rule 5 pursuant to the Treasury Clearing Rules would include much of the activity that is covered by these existing requirements. Therefore, FICC believes it is unnecessary to retain these trade submission requirements in the Rules with the adoption of the new requirements to Rule 5.</P>
                <P>In connection with this change FICC would delete the defined term “Covered Affiliate” from Rule 1.</P>
                <HD SOURCE="HD3">c. Retain Prohibition Against Pre-Netting Trade Data</HD>
                <P>FICC is proposing to move and consolidate the existing restriction against pre-netting practices from Section 3 of Rule 11 and Section 2 of Rule 18 into Section 4 of the new Rule 5. These provisions provide that any trade data that is required to be submitted to FICC must be submitted on a trade-by-trade basis with the original terms of the trade unaltered, and specifically prohibits pre-netting practices. The receipt of unaltered trade data permits FICC's market risk management processes to monitor trades closer to the time of execution and manage the risk exposures of those trades earlier in the day. Maintaining the prohibition against pre-netting practices for trades that are required to be submitted to FICC will, therefore, support the application of the risk management benefits of central clearing to this trading activity and support the goals of the Treasury Clearing Rules.</P>
                <P>
                    In moving and consolidating these provisions into Rule 5, FICC would also include the disciplinary action it may take if a Netting Member fails to comply with these requirements. Currently, Rules 11 and 18 provide that a Netting Member that violates this requirement “may be reported to the appropriate regulatory body, placed on the Watch List and/or subject to an additional fee” and that FICC may further discipline the Netting Member pursuant to Rule 48.
                    <SU>18</SU>
                    <FTREF/>
                     FICC is proposing to move these disciplinary measures to the new Section 4 of Rule 5.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         Section 3 of Rule 11, Section 2 of Rule 18, 
                        <E T="03">supra</E>
                         note 3. 
                        <E T="03">See also</E>
                         Rule 48 (addressing FICC's general authority to discipline any Member for violation of the Rules), 
                        <E T="03">id.</E>
                    </P>
                </FTNT>
                <P>In connection with this proposed change, FICC would also delete the defined term for “Pre-Netting of Trades” from Rule 1 as that term would be incorporated into the new Section 4 of Rule 5.</P>
                <HD SOURCE="HD3">2. Adopt Provisions To Monitor and Enforce the Trade Submission Requirement</HD>
                <P>
                    The proposed changes would adopt provisions to facilitate FICC's ability to identify and monitor the trade submission requirement. These proposed changes would clarify that FICC's existing ability to request information from both the Netting Member and from its applicable regulatory authority, and to review Netting Members' books and records, may be utilized by FICC, as and when it deems it necessary, to monitor Members' compliance with the 
                    <PRTPAGE P="42574"/>
                    requirement. The proposed changes would also adopt an affirmative obligation of Netting Members to proactively report any instances of non-compliance with the requirement, as described below.
                </P>
                <P>
                    While FICC would adopt provisions that would allow it to request information from Netting Members and their applicable regulatory authority, and to inspect Netting Members' books and records when it deems such review necessary, given that Netting Members' internal operations, organizational structures and trading practices vary greatly, FICC believes it is also appropriate to apply an approach that entails some degree of Netting Member self-reporting under the general obligation to comply with FICC's ongoing membership requirements. Therefore, and as recommended in the Adopting Release,
                    <SU>19</SU>
                    <FTREF/>
                     FICC is proposing to require that Netting Members monitor their own compliance with the requirement and report any instances of non-compliance, as described in detail below.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">Supra</E>
                         note 4, at 129 (“. . . U.S. Treasury securities CCA could require direct participants to submit to the CCA information regarding their U.S. Treasury securities transactions . . . .”).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">a. FICC's Authority To Request Information and Inspect Books and Records</HD>
                <P>FICC would describe in Section 2 of proposed Rule 5 its authority to take certain actions, and Netting Members' agreement to comply with such actions, in connection with its monitoring of Netting Members' ongoing compliance with the trade submission requirement. FICC currently has the authority to take each of these actions under Rules 2A and 3 in connection with its monitoring of Members' compliance with the requirements of membership generally. Therefore, FICC is not proposing to expand its authority to request information, or review the books and records of its Members, but would clarify that it may exercise these existing rights in connection with its monitoring of the trade submission requirement.</P>
                <P>
                    First, Netting Members would be required to submit to FICC any reports or other information that FICC may reasonably request, as also set forth in Section 2 of Rule 3, which requires that Netting Members submit to FICC “the reports, financial or other information set forth below and such other reports, financial and other information as the Corporation from time to time may reasonably require.” The proposed rule change would specify that this information could include, for example, reports of trading activity, trade data, and the Netting Member's policies, procedures or other controls related to its compliance with the trade submission requirement. Second, Netting Members would agree that FICC may inspect their books and records, as also set forth in Section 10 of Rule 3. Finally, Netting Members would authorize FICC to request information regarding a Netting Member from that firm's Designated Examining Authority or Appropriate Regulatory Agency, which FICC may also do under Rule 2A, Section 6 in evaluating an applicant to be a Netting Member. This provision would incorporate a suggestion in the Adopting Release that reviewing information from regulatory and self-regulatory organizations would be an appropriate method for FICC to assess its Netting Members' compliance with the requirement.
                    <SU>20</SU>
                    <FTREF/>
                     The proposed rule would specify that FICC may request information from such authority or agency as FICC deems necessary for the purposes of ensuring compliance with the trade submission requirement and as may be available to be shared, and that such information may include, for example, information related to such authority or agency's examination of the Netting Member's trading practices, trading reports and other records.
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See id.</E>
                         (“The Commission further agrees that a U.S. Treasury securities CCA also could review publicly available information and information made available to it by regulatory and self-regulatory organizations as part of its assessment of its direct participants' compliance.”).
                    </P>
                </FTNT>
                <P>As noted above and described below, FICC would primarily rely on Netting Members to monitor their own compliance with the trade submission requirement. However, these proposed changes to clarify FICC's existing rights to request information and examine Netting Members' books and records would allow FICC to verify such compliance, for example, before it takes action to enforce the requirement.</P>
                <HD SOURCE="HD3">b. Requirement To Notify FICC of Non-Compliance</HD>
                <P>
                    Second, the proposed rule changes would require each Netting Member to notify FICC in writing within 30 calendar days from the date on which it learns that it is no longer in compliance with the trade submission requirement. Currently, under Section 7 of Rule 3, Members are required to notify FICC if they are no longer in compliance with the qualifications, standards or other requirements of membership.
                    <SU>21</SU>
                    <FTREF/>
                     This proposed rule change would clarify for Members the application of this existing requirement to a failure to comply with the trade submission requirement, and would provide Netting Members with a longer period in which such notifications are required.
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Section 7 of Rule 3, 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>
                    The proposed rule change would also specify that notification of non-compliance shall include all relevant facts that are known to the Netting Member at the time of the notification and would identify examples of such information. Examples of such relevant facts would include (i) the approximate duration of the non-compliance with the trade submission requirement; (ii) either the time when non-compliance with the trade submission requirement was remediated or the anticipated steps to be taken to remediate such non-compliance and the approximate time when non-compliance is expected to remediated; and (iii) identification and contact information of the member of the Netting Member's Controlling Management (as such term is defined in the Rules) 
                    <SU>22</SU>
                    <FTREF/>
                     that is overseeing the matter.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See</E>
                         Rule 1 (“The term “Controlling Management” shall mean the Chief Executive Officer, the Chief Financial Officer, and the Chief Operations Officer, or their equivalents, of an applicant or Member or such other individuals or entities with direct or indirect control over the applicant or Member; provided that with respect to a Registered Investment Company Netting Member or an applicant to become a Registered Investment Company Netting Member, the term “Controlling Management” shall include the investment manager.”), 
                        <E T="03">supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>FICC believes this information would assist it in assessing the status and extent of the Netting Member's non-compliance with this requirement and the appropriate, applicable disciplinary measures. By requiring that a Netting Member identify a member of its Controlling Management that is overseeing the matter, the proposed rule change would ensure that the Netting Member has appropriately escalated the non-compliance internally and that the matter is being addressed by its senior management.</P>
                <HD SOURCE="HD3">c. Enforcement of Trade Submission Requirement</HD>
                <P>
                    Finally, Section 3 of proposed Rule 5 would provide that a Netting Member that fails to comply with the trade submission requirement would be subject to a fine under the Fine Schedule and that the Netting Member's Designated Examining Authority or Appropriate Regulatory Agency, as applicable, and the Commission would be notified of that failure. FICC believes that notice of a Netting Member's failure to comply with the trade submission requirement to other appropriate regulatory or self-regulatory 
                    <PRTPAGE P="42575"/>
                    organizations is an appropriate measure and would be an effective deterrent to non-compliance.
                </P>
                <P>Within the Fine Schedule, FICC would adopt a fine of $10,000 for failure to comply with the trade submission requirement. Section 3 of Rule 5 would provide Netting Members who notify FICC of their non-compliance with the trade submission requirement before such non-compliance is independently discovered by FICC with a cure period of 30 Business Days before the applicable disciplinary measures are taken. FICC believes it is appropriate to adopt this cure period to encourage Netting Members to effectively monitor their own compliance with the requirement and notify FICC when non-compliance is discovered.</P>
                <HD SOURCE="HD3">3. Other Revisions and Clarifications to the Rules</HD>
                <P>Finally, the proposed rule changes would make other revisions to clarify and conform provisions of the Rules to improve their accuracy and transparency.</P>
                <P>
                    First, the proposed rule changes would revise and clarify certain defined terms in Rule 1. The revisions would update the definition of “Affiliate” to replace a citation to a particular regulatory definition of this term set forth in rules promulgated under the Act, with the text of the particular regulatory definition of this term.
                    <SU>23</SU>
                    <FTREF/>
                     This revision would not change the meaning of this term as it is used in the Rules, but would provide further clarity by including the actual definition and not requiring a reader to find that definition in the cited regulation.
                </P>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         17 CFR 230.405.
                    </P>
                </FTNT>
                <P>
                    Second, the proposed rule change would define “Buy/Sell Transactions” in Rule 1 to mean a Transaction that is either the purchase or sale of an Eligible Netting Security in exchange for cash for which the trade data is submitted to FICC for Novation.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         The term “Buy/Sell Transaction” would also be used in the definition of “Bilateral Transaction” and “Brokered Transaction” in Rule 1 to clarify the meaning of those terms and would replace lowercase uses of this term in other places in the Rules with the proposed defined term. 
                        <E T="03">Supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>Third, the proposed rule changes would update the definition of “Designated Examining Authority” to include the appropriate regulatory bodies that may apply to other legal entity types and to permit FICC to choose the applicable regulatory body when a Member has multiple overseeing regulators. The additional regulatory authorities that would be included in this defined term are already listed along with the term Designated Examining Authority in Section 6 of Rule 3. Expanding the defined term to include these additional regulatory agencies in the defined term would allow FICC to remove that additional language from Rule 3 and simplify the uses of this term in other places in the Rules, including in Sections 2 and 3 of proposed Rule 5 regarding the monitoring and enforcement of the trade submission requirement.</P>
                <P>Fourth, the proposed rule changes would update the defined term for “Eligible Treasury Security” to clarify the meaning of this term by using the new proposed defined term for “U.S. Treasury Security” and the existing defined term for “Eligible Security.”</P>
                <P>Fifth, FICC would define “Treasury Repo Transaction” in Rule 1 to mean a Repo Transaction collateralized by Eligible Treasury Securities.</P>
                <P>Finally, FICC would adopt a new defined term for “U.S. Treasury Securities” in Rule 1 and would use this term in the definition of Eligible Treasury Security.</P>
                <HD SOURCE="HD3">Implementation Timeframe</HD>
                <P>Subject to approval by the Commission, FICC expects to implement the proposal, with the exception of the proposed changes to Rule 5 (to be renumbered Rule 6), and Rules 11, 15 and 18, by no later than December 31, 2026. FICC would announce the effective date of the proposed rule change by an Important Notice posted to FICC's website.</P>
                <P>While the Rules would be updated to reflect the majority of the changes proposed by no later than December 31, 2026, Netting Members would not be obligated to comply with the trade submission requirement proposed by this filing until the date set by the Commission as the relevant compliance date for cash transactions that are considered Eligible Secondary Market Transactions (“Eligible Buy/Sell Transactions Compliance Date”) and the date set by the Commission as the relevant compliance date for repurchase transactions that are considered Eligible Secondary Market Transactions (“Eligible Treasury Repo Transactions Compliance Date”), respectively.</P>
                <P>As noted in Exhibit 5 to this filing, the proposed changes to Rule 5 (to be re-numbered 6) and Rules 11 and 15 would be implemented on the Eligible Buy/Sell Transactions Compliance Date, and the proposed changes to Rule 18 would be implemented on the Eligible Treasury Repo Transactions Compliance Date.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    FICC believes the proposed changes are consistent with the requirements of the Act and the rules and regulations thereunder applicable to a registered clearing agency. In particular, FICC believes the proposed rule changes are consistent with Section 17A(b)(3)(F) and (G) of the Act,
                    <SU>25</SU>
                    <FTREF/>
                     and Rules 17ad-22(e)(18)(ii), (iii), (iv)(A) and (B), and (e)(23)(ii), each promulgated under the Act,
                    <SU>26</SU>
                    <FTREF/>
                     for the reasons described below.
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         15 U.S.C. 78q-1(b)(3)(F) and (G).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         17 CFR 240.17ad-22(e)(18)(ii), (iii), (e)(18)(iv)(A) and (B), and (e)(23)(ii).
                    </P>
                </FTNT>
                <P>
                    Section 17A(b)(3)(F) of the Act requires that the rules of FICC be designed to, among other things, promote the prompt and accurate clearance and settlement of securities transactions and assure the safeguarding of securities and funds which are in its custody or control or for which it is responsible.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <P>
                    The proposed rule changes to require that each Netting Member submit to FICC for Novation all Eligible Secondary Market Transactions to which it is a counterparty would promote the prompt and accurate clearance and settlement of securities transactions, consistent with Section 17A(b)(3)(F) of the Act, by ensuring that such transactions are subject to the risk mitigation benefits of central clearing at FICC. Such benefits are described by the Commission in the Adopting Release and include, for example, (1) reduction in overall counterparty credit risk when FICC Novates such transactions, becoming a counterparty to each transaction, as the buyer to every seller and the seller to every buyer; (2) enhancing the efficiency of, and market confidence in, centralized default management at FICC if a Netting Member defaults; and (3) increasing multilateral netting of these transactions, thereby reducing operational and other risks associated with such transactions.
                    <SU>28</SU>
                    <FTREF/>
                     By implementing the trade submission requirement and adopting provisions to monitor and enforce Members' compliance with that requirement, as required by the Treasury Clearing Rules, the proposal would extend the benefits of central clearing to all Eligible Secondary Market Transactions and, thereby, promote the prompt and accurate clearance and settlement of securities transactions, as recognized by the Adopting Release. In this way, the proposal is consistent with the 
                    <PRTPAGE P="42576"/>
                    requirements of Section 17A(b)(3)(F) of the Act.
                    <SU>29</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See supra</E>
                         note 4, at 14-18.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <P>
                    Section 17A(b)(3)(G) of the Act requires that the rules of FICC provide that its participants shall be appropriately disciplined for violation of any provision of the rules of the clearing agency by expulsion, suspension, limitation of activities, functions, and operations, fine, censure, or any other fitting sanction.
                    <SU>30</SU>
                    <FTREF/>
                     The proposed rule changes would adopt measures in proposed Rule 5 and in the Fine Schedule to address a failure to comply with the trade submission requirement. Under these provisions, FICC would impose a fine and notification to the applicable Netting Members' Designated Examining Authority or Appropriate Regulatory Agency and to the Commission. The disciplinary action would be clearly described in Rule 5, and the proposed fine amount would be set forth in the Fine Schedule. FICC is also proposing to adopt a cure period of 30 Business Days before it takes disciplinary measures if a Netting Member self-reports a failure to comply with the requirement. FICC believes these measures, including the cure period that would be available to Members who self-report a failure to comply with the trades submission requirements, are appropriate deterrents to non-compliance and are consistent with the requirements of Section 17A(b)(3)(G).
                    <SU>31</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         15 U.S.C. 78q-1(b)(3)(G).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    Rule 17ad-22(e)(18)(iv)(A) under the Act requires, among other things, that FICC, as a covered clearing agency that provides central counterparty services for transactions in U.S. Treasury Securities, require that any direct participant of such covered clearing agency submit for clearance and settlement all of the eligible secondary market transactions to which such direct participant is a counterparty.
                    <SU>32</SU>
                    <FTREF/>
                     The proposed rule changes would adopt a requirement that all Netting Members submit to FICC for clearing and settlement all Eligible Secondary Market Transactions to which they are a party, and would adopt the definition of Eligible Secondary Market Transactions as such term is defined in the Treasury Clearing Rules in defining the scope of this requirement. The proposed changes to adopt this requirement, and related defined terms, into Rules 1 and 5 would directly comply, and, therefore, be consistent, with the requirements of Rule 17ad-22(e)(18)(iv)(A).
                    <SU>33</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         17 CFR 240.17ad-22(e)(18)(iv)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    Rule 17ad-22(e)(18)(iv)(B) under the Act requires, among other things, that FICC, as a covered clearing agency that provides central counterparty services for transactions in U.S. Treasury Securities, identify and monitor its direct participants' submission of transactions for clearing as required by Rule 17ad-22(e)(18)(iv)(A), including how FICC would address a failure to submit transactions in accordance with Rule 17ad-22(e)(18)(iv)(A).
                    <SU>34</SU>
                    <FTREF/>
                     FICC is proposing to adopt provisions that would specify that its existing authority to request information and inspect its Netting Members' books and records would apply to its monitoring of their compliance with the trade submission requirement. FICC is also proposing to adopt an ongoing membership requirement that would require each Netting Member to report to FICC if the Netting Member is not in compliance with the trade submission requirement. As discussed above, FICC believes it is appropriate to identify and monitor Netting Members' submission of transactions for clearing by adopting both provisions that Netting Members take specific affirmative actions to review their compliance to FICC, and provisions that specify FICC's own authority to inspect and verify such compliance. Collectively, these provisions provide a comprehensive framework for identifying and monitoring compliance with the trade submission requirements and are consistent with the requirements of Rule 17ad-22(e)(18)(iv)(B).
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         17 CFR 240.17ad-22(e)(18)(iv)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    FICC is also proposing to adopt measures in proposed Rule 5 to specify how FICC would address a failure to comply with the trade submission requirement. Under these provisions, FICC would impose a fine and notification to the applicable Netting Members' Designated Examining Authority or Appropriate Regulatory Agency and to the Commission. FICC is also proposing to adopt a cure period of 30 Business Days before it takes disciplinary measures if a Netting Member self-reports a failure to comply with the requirement. FICC believes these measures, including the cure period, are appropriate deterrents to non-compliance and are consistent with the requirements of Rule 17ad-22(e)(18)(iv)(B).
                    <SU>36</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    Rule 17ad-22(e)(23)(ii) under the Act requires that FICC establish, implement, maintain and enforce written policies and procedures reasonably designed to provide for providing sufficient information to enable participants to identify and evaluate the risks, fees, and other material costs they incur by participating in FICC.
                    <SU>37</SU>
                    <FTREF/>
                     As described above, FICC is proposing a number of clarifications and revisions to the Rules that do not create new rights or obligations, but are designed instead to improve the clarity and transparency of the Rules. These proposed changes include clarifying existing defined terms and adopting new defined terms that create more consistency in how transactions are described in the GSD Rules. In this way, the proposed changes that are designed to clarify and conform provisions of the Rules are consistent with the requirements of Rule 17ad-22(e)(23)(ii).
                    <SU>38</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         17 CFR 240.17ad-22(e)(23)(ii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">(B) Clearing Agency's Statement on Burden on Competition</HD>
                <P>
                    The proposed rule changes to adopt a trade submission requirement and define the scope of that requirement by adopting definitions from the Treasury Clearing Rules could impose a burden on competition. Specifically, Netting Members that are subject to the trade submission requirement may incur additional costs related to submitting those transactions to FICC for central clearing, such as applicable clearing fees and risk management charges. These costs could burden Netting Members that have lower operating margins or higher costs of capital than other Netting Members or market participants. However, FICC believes that any burden on competition would be necessary and appropriate in furtherance of the purposes of the Act, as permitted by Section 17A(b)(3)(I) of the Act.
                    <SU>39</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         15 U.S.C. 78q-1(b)(3)(I).
                    </P>
                </FTNT>
                <P>
                    First, as described above, the proposed rule changes to adopt a trade submission requirement would be necessary in furtherance of the Act. By subjecting Eligible Secondary Market Transactions to the risk mitigation benefits of central clearing at FICC, including reducing overall counterparty credit risk, enhancing the efficiency of, and market confidence in, centralized default management at FICC if a Netting Member defaults, and increasing multilateral netting of these transactions, the proposed trade submission requirement would promote the prompt and accurate clearance and settlement of securities transactions, consistent with Section 17A(b)(3)(F) of the Act.
                    <SU>40</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <P>
                    As described above, the proposed trade submission requirement that 
                    <PRTPAGE P="42577"/>
                    would be adopted in proposed Rule 5 and the proposed scope of transactions that are subject to that requirement that would be adopted through the definition of “Eligible Secondary Securities Transactions” as such term is defined in the Exchange Act are necessary in furtherance of Rule 17ad-22(e)(18)(iv)(A) under the Act.
                    <SU>41</SU>
                    <FTREF/>
                     The proposed measures that address how FICC would identify and monitor Netting Members' compliance with the trade submission requirement and how FICC would address a failure to submit transactions in compliance with the trade submission requirement are also necessary in furtherance of Rule 17ad-22(e)(18)(iv)(B) under the Act.
                    <SU>42</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         17 CFR 240.17ad-22(e)(18)(iv)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         17 CFR 240.17ad-22(e)(18)(iv)(B).
                    </P>
                </FTNT>
                <P>
                    Second, FICC believes the proposed changes are appropriate in furtherance of the Act. Specifically, the proposed trade submission requirement would apply equally to all Netting Members, without any distinction between Members that are different legal entities or have different locations of incorporation, organizational structure or sizes. Under the proposed rules, which are being adopted to comply with the requirements of Rule 17ad-22(e)(18)(iv)(A), all Netting Members would be subject to the same obligation to submit Eligible Secondary Market Transactions to which they are a counterparty to FICC for clearing and settlement.
                    <SU>43</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         17 CFR 240.17ad-22(e)(18)(iv)(A).
                    </P>
                </FTNT>
                <P>
                    Similarly, the ongoing reporting requirement proposed to comply with the requirements of Rule 17ad-22(e)(18)(iv)(B) would apply to all Netting Members equally, without distinction.
                    <SU>44</SU>
                    <FTREF/>
                     The fines and regulatory reporting measures that FICC is proposing to adopt to address non-compliance with the trade submission requirement would also apply equally to all Netting Members. Finally, FICC is also proposing to adopt a cure period to incentivize Netting Members to self-report any non-compliance with the requirement. In these ways, FICC believes the proposed rule changes are appropriate and designed in a way to minimize the impact the proposal could have on competition.
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         17 CFR 240.17ad-22(e)(18)(iv)(B).
                    </P>
                </FTNT>
                <P>Therefore, while the proposed rule changes may cause some burden on competition, FICC believes that the proposed rule changes are necessary and appropriate in furtherance of the purposes of the Act.</P>
                <P>FICC does not believe the proposal to make technical corrections and other clarification changes to the Rules would impact competition. These changes are being proposed to ensure the clarity and accuracy of the Rules. They would not change FICC's current practices or affect Members' rights and obligations. As such, FICC believes those changes would not have any impact on competition.</P>
                <HD SOURCE="HD2">(C) Clearing Agency's Statement on Comments on the Proposed Rule Change Received From Members, Participants, or Others</HD>
                <P>FICC has not received or solicited any written comments relating to this proposal. If any written comments are received, they will be publicly filed as an Exhibit 2 to this filing, as required by Form 19b-4 and the General Instructions thereto.</P>
                <P>Persons submitting comments are cautioned that, according to Section IV (Solicitation of Comments) of the Exhibit 1A in the General Instructions to Form 19b-4, the Commission does not edit personal identifying information from comment submissions. Commenters should submit only information that they wish to make available publicly, including their name, email address, and any other identifying information.</P>
                <P>
                    All prospective commenters should follow the Commission's instructions on how to submit comments, available at 
                    <E T="03">www.sec.gov/rules-regulations/how-submit-comment.</E>
                     General questions regarding the rule filing process or logistical questions regarding this filing should be directed to the Main Office of the SEC's Division of Trading and Markets at 
                    <E T="03">tradingandmarkets@sec.gov</E>
                     or 202-551-5777.
                </P>
                <P>FICC reserves the right not to respond to any comments received.</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 self-regulatory organization 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">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-FICC-2026-007 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.</P>
                <FP>
                    All submissions should refer to File Number SR-FICC-2026-007. 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">www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the filing will be available for inspection and copying at the principal office of FICC and on DTCC's website (
                    <E T="03">www.dtcc.com/legal/sec-rule-filings</E>
                    ). 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-FICC-2026-007 and should be submitted on or before July 30, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>45</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>45</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13827 Filed 7-8-26; 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-105850; File No. SR-LCH SA-2026-004]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; LCH SA; Notice of Filing of Proposed Rule Change Relating to the LCH SA Liquidity Plan</SUBJECT>
                <DATE>July 6, 2026.</DATE>
                <P>
                    Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 
                    <PRTPAGE P="42578"/>
                    (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on June 22, 2026, Banque Centrale de Compensation, which conducts business under the name LCH SA (“LCH SA”), 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 clearing agency. 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. Clearing Agency's Statement of the Terms of Substance of the Proposed Rule Change</HD>
                <P>
                    LCH SA is submitting the LCH SA Liquidity Plan (the “Liquidity Plan”), which sets out the principles and procedures for liquidity management within LCH SA, as part of its 2025 annual review. The Liquidity Plan has been adopted by the LCH SA Risk Committee and LCH SA Board 
                    <SU>3</SU>
                    <FTREF/>
                     (the “Proposed Rule Change”).
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The Liquidity Plan has been elaborated in common with LCH Limited in order to ensure risk management consistency within the LCH Group.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         All capitalized terms not defined herein have the same meaning as in the Rule Book or Procedures, as applicable, in their version as available on LCH SA's website: 
                        <E T="03">https://www.lseg.com/en/post-trade/clearing/clearing-resources/rulebooks/lch-sa.</E>
                    </P>
                </FTNT>
                <P>The text of the Proposed Rule Change has been annexed [sic] as Exhibit 5 to File No. SR-LCH SA-2026-004.</P>
                <P>The implementation of the Proposed Rule Change will be contingent on LCH SA's receipt of the SEC regulatory approval.</P>
                <HD SOURCE="HD1">II. Clearing Agency's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change</HD>
                <P>In its filing with the Commission, LCH SA included statements concerning the purpose of and basis for the Risk Policies and discussed any comments it received on the Risk Policies. The text of these statements may be examined at the places specified in Item IV below. LCH SA 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 Liquidity Plan has been adopted by LCH SA in order to set out the specific principles and procedures for liquidity management that govern its operations as a clearing agency. The Liquidity Plan has been designed to ensure consistency with all relevant laws and regulations, including the European Markets Infrastructure Regulation (EMIR) 
                    <SU>5</SU>
                    <FTREF/>
                     and Section 17A of the Act 
                    <SU>6</SU>
                    <FTREF/>
                     and the regulations thereunder.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Regulation (EU) No 648/2012 of the European Parliament and of the Council of 4 July 2012 on Over-the-Counter derivatives, central counterparties and trade repositories (“EMIR”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78q-1.
                    </P>
                </FTNT>
                <P>
                    The objectives of the Liquidity Plan are to ensure: (i) the effective management of liquidity by adhering to the appropriate governance structure to manage liquidity risk, including reporting lines and accountabilities; (ii) the liquidity adequacy of LCH SA at all times in accordance with policies set by the appropriate governance authority and monitored and reported by LCH SA Risk Department; (iii) that liquidity management and resources are aligned with LCH SA operational requirements to meet payment obligations as they fall due under business as usual and stressed liquidity conditions; (iv) effective liquidity risk identification and escalation within Collateral and Liquidity Management (“CaLM”) 
                    <SU>7</SU>
                    <FTREF/>
                     and the other departments within LCH SA identified in the Liquidity Plan; and (v) that systems and processes are in place to facilitate effective management of liquidity risk.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         CaLM's responsibilities include: (i) managing LCH SA's collateral and liquidity positions, including ensuring sufficient liquidity, investment of cash collateral, and maintaining market, credit, and operational controls; (ii) acting as the first line of defence for collateral and liquidity, managing business risk, default management inputs, and adherence to LCH SA policies; (iii) monitoring limits, managing exposures, and coordinating with Second Line CaLM Risk, described in greater detail in note 12, 
                        <E T="03">infra;</E>
                         (iv) supporting regulatory engagement and compliance, including providing inputs for SEC filings, EMIR considerations, governance, and risk reporting; and (v) overseeing operational resilience and service performance, including steady state operations reviews, incident management, and change governance.
                    </P>
                </FTNT>
                <P>
                    The Liquidity Plan sets out the roles and responsibilities within LCH SA for compliance with the Liquidity Plan, primary responsibility for which falls to CaLM. Specifically, the Liquidity Plan clarifies that: (i) the LCH SA Head of CaLM (or its delegate) is responsible for maintaining the Liquidity Plan, overseeing the portfolio management function, and is responsible for the overall liquidity position and adherence to the Liquidity Plan and relevant policies; 
                    <SU>8</SU>
                    <FTREF/>
                     (ii) CaLM Front Office,
                    <SU>9</SU>
                    <FTREF/>
                     comprised of trading personnel, is responsible for day-to-day investment activities, intraday liquidity management and monitoring, and oversight of asset encumbrance requirements including pledged assets and Futures Commission Merchant (“FCM”) non-cash collateral; (iii) Second Line CaLM Risk 
                    <SU>10</SU>
                    <FTREF/>
                     sets liquidity risk limits, enforces liquidity risk limits and escalates limit breaches, develops and enhances the liquidity risk management framework, and identifies, measures, monitors, and reports liquidity risks; (iv) Collateral Operations 
                    <SU>11</SU>
                    <FTREF/>
                     is responsible for the operational and control processes 
                    <PRTPAGE P="42579"/>
                    related to intraday liquidity flows and performs intraday monitoring of CaLM investment activity; and (v) CaLM Middle Office 
                    <SU>12</SU>
                    <FTREF/>
                     is responsible for mark-to-market of the CaLM SA portfolio and formal reporting of CaLM investment activity.
                    <SU>13</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The responsibilities of the LCH SA Head of CaLM (or its delegate) also include: (i) escalation to the LCH SA CEO, the Local Management Committee (which is a senior governance forum within LCH SA's legal entity governance structure, responsible for overseeing management, risk, governance, and performance issues, including Liquidity Plan adherence and significant liquidity or investment concerns escalated from CaLM), LCH SA Risk Management, and the LCH SA Board, where appropriate; (ii) initial declaration of a liquidity event, and for the initial escalation of liquidity issues arising from a declared liquidity event; (iii) decide on the need for, and the subsequent conduction of a crisis call if liquidity issues are not resolved as part of the liquidity event; (iv) select and convene the Liquidity Crisis Management Team (which is a cross-functional liquidity crisis structure activated during stress or default events, typically via the Default Management Group, and is responsible for monitoring and managing liquidity positions during a member default), executing the auction and collateral liquidation processes, and coordinating across relevant functions under crisis conditions); (v) adequately supervise CaLM investment personnel; (vi) maintain and update the Liquidity Plan; (vii) sign-off of any new product approval with respect to liquidity and investment considerations; and (viii) accountability for due diligence and testing of liquidity providers.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         CaLM Front Office is a front office investment function within CaLM, forming part of the “first line of defense” responsible for managing LCH SA's investment and liquidity activities. Its responsibilities include investing cash collateral received from clearing members and managing the liquidity, credit, and interest rate risks of LCH SA's cash portfolio, escalating any liquidity or investment concerns, executing daily funding, portfolio actions, repo investments, and supporting default management liquidity needs. CaLM Front Office also supports the auction and collateral liquidation elements of the default management process.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Second Line CaLM Risk conducts a monitoring and reporting function on CaLM investment and liquidity management activities and sits at the CCP level, reporting to the LCH SA Chief Risk Officer.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         Collateral Operations is a function within CaLM responsible for the day-to-day operational management of collateral posted to LCH SA. This includes processing and validating deposits and withdrawals of cash and non-cash collateral, performing reconciliations and controls to prevent fraud, unauthorised manual entries, or booking errors, and supporting settlement, custody, and payment flows that connect directly to CaLM's investment and liquidity processes. Collateral Operations also provides operational input into liquidity actions, member withdrawals, and margin-related collateral movements.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         CaLM Middle Office provides control, booking, and operational oversight. Its responsibilities include flash NTI and non-cash collateral income reporting, ensuring adherence to limits, controls, and segregation of duties as part of the CaLM control framework, and supporting risk reporting, liquidity forecasting processes, and data integrity for CaLM.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         CaLM must ensure that the daily available cash amount is compliant with the LCH SA's Operational Liquidity Target, which is set and monitored by Second Line CaLM Risk.
                    </P>
                </FTNT>
                <P>
                    The Liquidity Plan also provides that CaLM First Line Risk 
                    <SU>14</SU>
                    <FTREF/>
                     is responsible for the daily pricing of the liquid assets and investment portfolio. Regular reporting is distributed by CaLM Middle Office to relevant stakeholders through downstream systems, including a CaLM Investment Report for the clearing agency on a daily and monthly basis. Second Line CaLM Risk conducts the monitoring and reporting of these activities, as described immediately above. The LCH SA Chief Risk Officer is responsible for taking and deciding any relevant actions during a liquidity event.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         CaLM First Line Risk manages and assesses investment, liquidity, credit and interest rate risks of the total collateral portfolio, produces liquidity needs reporting in case of default, and assesses liquidity and risk implications of proposed new eligible collateral types.
                    </P>
                </FTNT>
                <P>
                    The Liquidity Plan identifies the different sources and availability of liquidity,
                    <SU>15</SU>
                    <FTREF/>
                     including: (i) cash posted by members to meet margin requirements; (ii) cash contributions to Default Funds; (iii) LCH SA's own capital; (iv) excess cash placed by members; and (v) cash arising from settlement fails. The primary sources of liquidity for LCH SA are the cash posted by its members to meet margin requirements, the cash contributions to Default Funds, as well as LCH SA's own capital.
                    <SU>16</SU>
                    <FTREF/>
                     In addition, LCH SA may use available central bank arrangements to generate same-day liquidity by pledging non-cash collateral deposited by its members on a title transfer basis through the central bank window.
                    <SU>17</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         Cash margin is invested either via overnight deposit at Banque de France or through secured repos and outright purchase of bonds under the LCH Investment Risk Policy. Available liquidity resources are readily convertible into cash through pre-arranged mechanisms, including repo and, where applicable, access to central bank liquidity.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Segregated client funds are excluded as a general source of liquidity in accordance with CFTC Rule 1.25.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         As a French banking institution, LCH SA has access through the Euro system to the open market operations and the standing facilities of the ECB and the Banque de France, which are available to eligible counterparties on their own initiative, subject to their fulfilment of certain operational access conditions.
                    </P>
                </FTNT>
                <P>More broadly, the Liquidity Plan specifies that available liquidity resources include: (i) maturing transactions from reverse repo and overnight unsecured investments; (ii) sale of portfolio of highly liquid assets; (iii) maturity and/or redemption of on-demand investments; (iv) repo of highly liquid securities; (v) borrowing facilities; (vi) foreign exchange (“FX”) funding transactions; and (vii) access to central bank liquidity.</P>
                <P>The Liquidity Plan also identifies other potential scenarios which could impact the liquidity resources available to meet liquidity requirements, including: (i) cash tied in investment activities which cannot be freed in time to meet requirements; (ii) disruption in the cash bond/repo market which delays mobilisation of a defaulted member's non-cash collateral; (iii) payment flow delays; (iv) International Central Securities Depository (“ICSD”) credit lines reduced or not available; and (v) cash/non-cash that is provided for interoperability arrangement purposes.</P>
                <P>
                    To mitigate such potential draws on liquidity, the Liquidity Plan sets out additional methods to retain liquidity within LCH SA. These include: (i) increasing the substitution notice period; (ii) utilising intraday liquidity available at Central Securities Depositories (“CSDs”); (iii) prioritising the return of non-cash over cash collateral; (iv) applying caps on pledge amounts and non-Euro securities; (v) imposing service level cash primary liquid resources requirements; and (vi) making extraordinary margin calls if the Liquidity Coverage Ratio (“LCR”) falls below specified thresholds.
                    <SU>18</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         The latest version of the LCH SA Liquidity Plan does not include, as a method to retain liquidity with LCH SA, disabling of auto repay because LCH SA is currently considering the proper scope of that potential method.
                    </P>
                </FTNT>
                <P>
                    The Liquidity Plan describes the steps LCH SA takes to assess its liquidity position. The liquidity assessment, as specified in the LCH SA Liquidity Risk Policy 
                    <SU>19</SU>
                    <FTREF/>
                     must be run: (i) daily at an aggregated level and on all material currencies; (ii) over a forward liquidity period; and (iii) intraday at various times when LCH SA has scheduled obligations to pay. The assessment must also factor in regulatory restrictions on the use and liquidation of client assets maintained in segregated accounts and consider stress scenarios that include restricted market access and behavioural assumptions on how members may withdraw cash during times of stress.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         See Exchange Act Release No. 104980 (March 12, 2026), 91 FR 12869 (March. 17, 2026) (SR-LCH SA-2025-010), which approved the LCH SA Liquidity Risk Policy.
                    </P>
                </FTNT>
                <P>
                    Building on that assessment, the Liquidity Plan specifies a comprehensive liquidity stress-testing framework. This includes daily liquidity stress testing for Cover 2 
                    <SU>20</SU>
                    <FTREF/>
                     default by currency, intraday Cover 2 default liquidity stress testing when LCH SA has scheduled obligations to pay, and at least a 5-day forward looking Cover 2 default liquidity stress test. Additional stress scenarios following a Cover 2 default include a liquidity squeeze affecting Tier 1 and Tier 2 collateral or increased Central Bank haircuts, and a flight to quality impacting Tier 2 and Tier 3 collateral while Tier 1 collateral remains unaffected through Central Bank facilities.
                    <SU>21</SU>
                    <FTREF/>
                     The framework also includes Euronext Clearing liquidity stress testing and Cover 1 
                    <SU>22</SU>
                    <FTREF/>
                     stress testing to demonstrate compliance with 
                    <PRTPAGE P="42580"/>
                    SEC rules and U.S. established practices.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         “Cover 2” refers to the regulatory standard requiring a CCP to maintain sufficient liquid resources to cover the liquidity needs arising from the simultaneous default of the two clearing member groups that would generate the largest aggregate payment obligations under extreme but plausible market conditions.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         As mentioned in the LCH SA Liquidity Risk modelling Framework, “Tier 1,” “Tier 2,” and “Tier 3” collateral refer to LCH SA's internal collateral liquidity tiers, which are classified based on certain liquidity and eligibility criteria. For purposes of “Cover 2” testing, Tier 1 collateral comprises assets of the highest liquidity quality, including all ECB-eligible collateral, Gilts, US Treasuries, and central bank guarantees from the Dutch and Belgian central banks (but only when posted by members domiciled in the same country as the guaranteeing central bank and only in the case of default of such members posting the central bank guarantee). These assets are considered to be readily monetisable, typically via same-day central bank facilities or repo transactions for Gilts and US Treasuries and are used as primary liquidity resources in stress scenarios. Tier 3 collateral comprises assets with little or no liquidity value in a default or stressed market scenario, or those considered too illiquid to be converted within the required timeframe, including equities, central bank guarantees posted by non-defaulting members, and non-cash collateral denominated in DKK, NOK, SEK, JPY, CHF, CAD, and AUD. These assets are not included as liquidity resources in the liquidity stress testing. There are currently no assets classified as Tier 2 collateral, reflecting a conservative approach whereby only the most liquid and readily monetisable assets are included in Tier 1 and less liquid or ineligible assets are directly classified as Tier 3. Note that, for “Cover 1” testing, defined in note 22, infra, and in accordance with LCH SA's obligations as a registered clearing agency, Gilts and US Treasuries are currently classified as Tier 3 and are therefore excluded from the qualifying liquid resources.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         “Cover 1” refers to the regulatory standard requiring a CCP to maintain sufficient liquid resources to cover the liquidity needs arising from the default of the single clearing member group that would generate the largest aggregate payment obligation under extreme but plausible market conditions.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         For cross-currency triparty repo, qualifying liquid resources are included in LCR Cover 2 calculations but excluded from LCR Cover 1.
                    </P>
                </FTNT>
                <P>In addition, the Liquidity Plan also includes liquidity reverse stress scenarios, which model: (i) reductions in cash margin to generate a liquidity deficit; (ii) switches to non-liquid resources; (iii) rating downgrades of Euro zone peripheral and core countries; (iv) increased outflows due to mark-to-market moves of assets; (v) multiple defaults of low credit worthiness members; (vi) Euronext Clearing variation margins; (vii) increases in the maturity of securities from margin collateral and settlement of repo transactions; and (viii) combined behavioural and macroeconomic scenarios.</P>
                <P>
                    In terms of liquidity demands, the Liquidity Plan clarifies that LCH SA's two main sources of liquidity need are: operational liquidity and default liquidity.
                    <E T="51">24 25</E>
                    <FTREF/>
                     Operational liquidity needs include repayment of excess cash collateral to members, substitution of cash collateral upon member request, provision of liquidity to facilitate settlement (including fails), potential planned Default Fund reductions, overall reductions in Initial Margin and thus cash posted for margin coverage, and Euronext Clearing variation margin outflows.
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         The Liquidity Plan specifies that if a member defaults, the collateral posted by the defaulted member is used to cover any mark-to-market loss during the liquidation of the portfolio.
                    </P>
                    <P>
                        <SU>25</SU>
                         The LCH SA Default Management Policy and framework provides detailed guidance in relation to Default Management.
                    </P>
                </FTNT>
                <P>
                    To support intraday operational liquidity needs, the Liquidity Plan specifies that LCH SA maintains three main separate pools of collateral: (i) the Euroclear Bank credit line, under which, on the basis of ECB eligible and non-eligible collateral, liquidity can be created to finance settlements in Euroclear Bank's platform enabling settlements in Euroclear France, Euroclear Belgium and Euroclear Netherlands; (ii) the Clearstream Bank Luxembourg credit line (including Clearstream Banking Frankfurt and Clearstream Banking Luxembourg), under which, on the basis of ECB eligible and noneligible collateral, liquidity can be created to finance domestic and cross border settlements. In addition, the T2S auto-collateralization system generates intraday liquidity to facilitate the settlement of Italian, French, Spanish, German and Belgian repo transactions, and the Banque de France Global Collateral Management; and (iii) the “3G”, credit line 
                    <SU>26</SU>
                    <FTREF/>
                     is available for intraday liquidity and overnight access if needed.
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         This refers to LCH SA's secured central bank credit line with Banque de France, available intraday and overnight, under which ECB-eligible securities are pledged to the Banque de France 3G collateral pool to raise Euro cash.
                    </P>
                </FTNT>
                <P>The Liquidity Plan specifies that Collateral Operations monitors daily liquidity flows on a day-to-day basis, with the 9:30 a.m. observation identified as the most accurate indicator of daily operational liquidity requirements since all margin returns to members occur in the morning. Intraday margin calls later in the day result in inflows that are generally invested on an overnight basis and matched by corresponding outflows the following day. If an operational liquidity shortfall is not fully met with maturing transactions, CaLM has a range of options to generate liquidity, with the choice and prioritisation depending on the timing and duration of liquidity requirements and market conditions.</P>
                <P>
                    To generate liquidity, the Liquidity Plan sets out the options available to LCH SA, structured by priority. For Euro currency, the primary and preferred options include: (i) Euro cash collateral; and (ii) transfer of Euro non-cash securities (collateral and portfolio) to the Banque de France 3G credit line. Secondary options include bilateral or triparty repo of Euro assets. As a last resort, LCH SA may access: (i) the overnight standing facility with the Banque de France (marginal lending facility) to obtain overnight Euro liquidity against the presentation of sufficient eligible assets; (ii) term reverse transactions with the Banque de France, including Main Refinancing Operations (one-week maturity) or Longer-Term Refinancing Operations (three-month maturity); 
                    <SU>27</SU>
                    <FTREF/>
                     and (iii) uncommitted credit lines. For non-Euro currencies, the primary and preferred option is non-Euro cash collateral. Repo transactions serve as a secondary option, including bilateral repo transactions and cross-currency triparty repo (non-Euro cash taker and Euro collateral giver). As a last resort, LCH SA may access uncommitted credit lines with a major international bank for a multi-currency credit line in the form of an overdraft, or the ECB weekly tender in USD given LCH SA's banking status.
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         Main refinancing operations are regular reverse transactions that provide liquidity, usually with a frequency and duration of one week. Longer-term refinancing operations are reverse transactions that provide liquidity for a longer duration than the main refinancing operations, with a maturity of three months conducted on a monthly basis by the Euro system.
                    </P>
                </FTNT>
                <P>For the second major source of liquidity needs, default liquidity, LCH SA's needs encompass fulfilment of the settlement obligations of a defaulted clearing member, posting of variation margins to non-defaulting members on positions held by a defaulted clearing member, and potential losses due to the liquidation of cleared positions and collateral lodged by the defaulting member. In terms of default liquidity management, the Liquidity Plan provides that, in the event of a member default, LCH SA may face even greater liquidity requirements spread over a period of several days. For Euro currency under default management, the options include the use of Euro cash collateral as the first source, followed by the transfer of Euro securities (collateral, clearing and portfolio) to the Banque de France credit line as the primary and preferred option. The Liquidity Plan notes that LCH SA has full title of transfer on securities lodged as collateral (except for members using pledged accounts or FCM client collateral) or sourced via CSD to settle RepoClear transactions on behalf of the defaulter. Additional options include the sale of the defaulter's Euro non-cash collateral to realise cash value, and repo transactions (bilateral, triparty, or cross-currency triparty). For non-Euro currencies under default management, the primary options are non-Euro cash collateral and the sale of the defaulter's non-Euro non-cash collateral. The Liquidity Plan also provides for FX spot transactions as a secondary option, framed by the Global Risk Investment Policy for settlement of non-Euro liabilities, as well as repo transactions. As a last resort for both Euro and non-Euro default liquidity needs, LCH SA may access uncommitted credit lines and, for Euro and USD, central bank facilities including the ECB weekly tender in USD.</P>
                <P>
                    To evidence ongoing access and readiness, CaLM undertakes “War Games” testing to ensure that assumptions around activities used in stressed environments to raise liquidity are realistic. The testing activities fall into three categories. The first covers activities carried out under business as usual, such as the sale of securities, which demonstrate execution procedures and identify which counterparties have appetite. The second covers activities not relied on in day-to-day liquidity management but tested to demonstrate access to liquidity, such as repo transactions and access to Central Bank facilities; these are tested in relatively small size to verify procedures for execution and 
                    <PRTPAGE P="42581"/>
                    demonstrate access as a source of liquidity. The third covers activities that cannot be fully tested through execution but are tested through simulation, such as simulating the liquidation of a defaulting member's collateral portfolio by asking counterparties to show bid prices in a “what if” scenario. CaLM tests with each liquidity provider, to the extent practicable, the access of the relevant liquidity resources used for assessing the liquidity position, not less than once every 12 months with respect to qualifying liquid resources.
                </P>
                <P>
                    The Liquidity Plan also describes the mechanics for replenishment of cash following liquidity usage. The primary source of cash to mitigate any liquidity shortfall is cash margin collateral posted by members, together with ECB eligible securities that can be converted into cash through the central bank.
                    <SU>28</SU>
                    <FTREF/>
                     During default management, LCH SA may need to make payments on behalf of the defaulter to cover variation margins, settlement obligations, and hedging costs. If a member defaults, the collateral posted by the defaulted member is used to cover any mark-to-market loss during the liquidation of the portfolio. To complete settlement of cleared contracts, LCH SA will source the required liquidity either from the pool of cash posted by members (margin and default fund contributions) or by utilising bonds under the cleared contract or from the non-cash collateral pool to raise liquidity through the Banque de France 3G credit line or repo transactions. The bond acquired is then sold in the auction and the proceeds used to replenish liquidity. If the bond is sold at a lower value than the cash paid under the repo, the resulting mark-to-market loss is covered by the default waterfall.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         The source of cash LCH SA uses to mitigate any liquidity shortfall is primarily the cash margin collateral posted by members as well as ECB eligible securities that can be converted into cash through the central bank thanks to LCH SA's banking license.
                    </P>
                </FTNT>
                <P>Finally, the Liquidity Plan requires LCH SA to undertake due diligence on each of its liquidity providers to assess the relevant provider's capacity to understand and manage its own liquidity risk as well as its ability to perform under its commitments to provide liquidity to LCH SA. The scope of this due diligence extends to CSDs and ICSDs, central banks, and CaLM counterparties, in each case where such entities act as liquidity providers of LCH SA.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    LCH SA has determined that the Liquidity Plan is consistent with the requirements of Section 17A of the Act 
                    <SU>29</SU>
                    <FTREF/>
                     and regulations thereunder applicable to it, including the requirements of Commission Rule 17ad-22(e)(7).
                    <SU>30</SU>
                    <FTREF/>
                     In particular, Section 17A(b)(3)(F) of the Act requires, 
                    <E T="03">inter alia,</E>
                     that the rules of a clearing agency “promote the prompt and accurate clearance and settlement of securities transactions” and “assure the safeguarding of . . . funds which are in the custody or control of the clearing agency or for which it is responsible.” 
                    <SU>31</SU>
                    <FTREF/>
                     The Liquidity Plan establishes comprehensive standards for liquidity management that ensure LCH SA maintains sufficient liquid resources to meet its payment obligations as they fall due, thereby promoting prompt and accurate clearance and settlement and safeguarding securities and funds in its custody or control. As such, the Liquidity Plan is consistent with Section 17A(b)(3)(F) of the Act.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         15 U.S.C. 78q-1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         17 CFR 240.17ad-22(e)(7).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         15 U.S.C. 78q-1(b)(3)(F).
                    </P>
                </FTNT>
                <P>
                    Commission Rule 17ad-22(e)(7) 
                    <SU>32</SU>
                    <FTREF/>
                     requires each covered clearing agency to establish, implement, maintain, and enforce written policies and procedures reasonably designed to effectively measure, monitor, and manage the liquidity risk that arises in or is borne by the covered clearing agency, including measuring, monitoring, and managing its settlement and funding flows on an ongoing and timely basis, and its use of intraday liquidity. The Liquidity Plan addresses certain of the requirements in Rule 17ad-22(e)(7) as set forth in greater detail below.
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         17 CFR 240.17ad-22(e)(7).
                    </P>
                </FTNT>
                <P>
                    Commission Rule 17ad-22(e)(7)(i) requires a covered clearing agency to maintain “sufficient liquid resources at the minimum in all relevant currencies to effect same-day and, where appropriate, intraday and multiday settlement of payment obligations with a high degree of confidence under a wide range of foreseeable stress scenarios that includes, but is not limited to, the default of the participant family that would generate the largest aggregate payment obligation for the covered clearing agency in extreme but plausible market conditions”.
                    <SU>33</SU>
                    <FTREF/>
                     The Liquidity Plan identifies the primary sources of liquidity for LCH SA, including cash posted by clearing members to meet margin requirements, cash contributions to Default Funds, and LCH SA's own capital. In addition, the Liquidity Plan provides that LCH SA may use available Central Bank arrangements to generate same-day liquidity by pledging non-cash collateral deposited by its members on a title transfer basis through the Central Bank window. To support intraday liquidity needs, the Liquidity Plan specifies that LCH SA maintains multiple pools of collateral supporting different activities, including credit lines with Euroclear Bank, and Clearstream Bank Luxembourg, the T2S auto-collateralisation system for facilitating settlement of repo transactions, and the Banque de France 3G credit line available for both intraday and overnight liquidity needs.
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         17 CFR 240.17ad-22(e)(7)(i).
                    </P>
                </FTNT>
                <P>Further, the Liquidity Plan establishes a comprehensive liquidity stress-testing framework that includes daily liquidity stress testing for Cover 2 default by currency, intraday Cover 2 default liquidity stress testing when LCH SA has scheduled obligations to pay, and at least a 5-day forward-looking Cover 2 default liquidity stress test. Additional stress scenarios include a liquidity squeeze affecting Tier 1 and Tier 2 collateral or increased Central Bank haircuts, and a flight to quality impacting Tier 2 and Tier 3 collateral while Tier 1 collateral remains unaffected through Central Bank facilities. The Liquidity Plan also includes Cover 1stress testing to demonstrate compliance with SEC rules and U.S. established practices. The Liquidity Plan further specifies that the liquidity assessment must be run: (i) daily at an aggregated level and on all material currencies; (ii) over a forward liquidity period; and (iii) intraday at various times when LCH SA has scheduled obligations to pay. The assessment must factor in regulatory restrictions on the use and liquidation of client assets maintained in segregated accounts and consider stress scenarios that include restricted market access and behavioural assumptions on how members may withdraw cash during times of stress. By requiring LCH SA to maintain sufficient liquid resources in all relevant currencies, to assess its liquidity position on a daily and intraday basis, and to conduct liquidity stress testing that models the default of the two member groups with the largest liquidity requirement under extreme but plausible market conditions, the Liquidity Plan is consistent with Commission Rule 17ad-22(e)(7)(i).</P>
                <P>
                    Commission Rule 17ad-22(e)(7)(ii) requires a covered clearing agency to hold “qualifying liquid resources sufficient to meet the minimum liquidity resource requirement under paragraph (e)(7)(i) in each relevant currency for which the covered clearing agency has payment obligations owed to 
                    <PRTPAGE P="42582"/>
                    clearing members.” 
                    <SU>34</SU>
                    <FTREF/>
                     The Liquidity Plan identifies the qualifying liquid resources available to LCH SA in each relevant currency. For Euro currency, qualifying liquid resources include Euro cash collateral and the transfer of Euro non-cash securities to the Banque de France 3G credit line. For non-Euro currencies, the Liquidity Plan provides that qualifying liquid resources include non-Euro cash collateral. The Liquidity Plan further specifies the options available to generate liquidity in both Euro and non-Euro currencies, structured by priority, including repo transactions, access to Central Bank facilities, and uncommitted credit lines. The Liquidity Plan also includes liquidity reverse stress scenarios that model reductions in cash margin to generate a liquidity deficit, switches to non-liquid resources, rating downgrades of Euro zone peripheral and core countries, increased outflows due to mark-to-market moves of assets, multiple defaults of low credit worthiness members, and combined behavioural and macroeconomic scenarios. By identifying the qualifying liquid resources available to LCH SA in each relevant currency and establishing a framework for maintaining sufficient qualifying liquid resources to meet the minimum liquidity resource requirement, the Liquidity Plan is consistent with Commission Rule 17ad-22(e)(7)(ii).
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         17 CFR 240.17ad-22(e)(7)(ii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         17 CFR 240.17ad-22(e)(7)(ii).
                    </P>
                </FTNT>
                <P>
                    Commission Rule 17ad-22(e)(7)(iii) requires a covered clearing agency to use “access to accounts and services at a Federal Reserve Bank, pursuant to Section 806(a) of the Payment, Clearing, and Settlement Supervision Act of 2010, or other relevant central bank, when available and where determined to be practical by the board of directors of the covered clearing agency, to enhance its management of liquidity risk.” 
                    <SU>36</SU>
                    <FTREF/>
                     The Liquidity Plan provides that, as a French banking institution, LCH SA has access through the Euro system to the open market operations and standing facilities of both the ECB and the Banque de France, which are available to eligible counterparties on their own initiative, subject to their fulfilment of certain operational access conditions. The Liquidity Plan specifies that the primary and preferred option for generating Euro liquidity is the transfer of Euro non-cash securities to the Banque de France using its 3G credit line.
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         17 CFR 240.17ad-22(e)(7)(iii).
                    </P>
                </FTNT>
                <P>
                    The Liquidity Plan further provides that LCH SA may access the overnight standing facility with the Banque de France (marginal lending facility) to obtain overnight Euro liquidity against the presentation of sufficient eligible assets, as well as term reverse transactions with the Banque de France, including Main Refinancing Operations and Longer-Term Refinancing Operations. Given its banking status, LCH SA also has access to U.S. Dollar liquidity through the ECB's open market operations. By providing for LCH SA's access to and use of central bank accounts and services to enhance its management of liquidity risk, the Liquidity Plan is consistent with Commission Rule 17ad-22(e)(7)(iii).
                    <SU>37</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         17 CFR 240.17ad-22(e)(7)(iii).
                    </P>
                </FTNT>
                <P>
                    Commission Rule 17ad-22(e)(7)(iv) requires a covered clearing agency to undertake “due diligence to confirm that it has a reasonable basis to believe each of its liquidity providers has: (a) sufficient information to understand and manage the liquidity provider's liquidity risks and (b) the capacity to perform as required under its commitments to provide liquidity to the covered clearing agency.” 
                    <SU>38</SU>
                    <FTREF/>
                     The Liquidity Plan provides that LCH SA shall undertake due diligence on each of its liquidity providers to assess the capacity of the provider to understand and manage its liquidity risk and its capacity to perform under its commitments to provide liquidity to LCH SA. The entities included in the scope of due diligence include CSDs and ICSDs, Central Banks, and CaLM counterparties, if they act as liquidity providers of LCH SA. By requiring LCH SA to undertake due diligence on its liquidity providers, the Liquidity Plan is consistent with Commission Rule 17ad-22(e)(7)(iv).
                    <SU>39</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         17 CFR 240.17ad-22(e)(7)(iv).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         17 CFR 240.17ad-22(e)(7)(iv).
                    </P>
                </FTNT>
                <P>
                    Commission Rule 17ad-22(e)(7)(v) requires a covered clearing agency to “maintain[ing] and test[ing] with each liquidity provider, to the extent practicable, the covered clearing agency's procedures and operational capacity for accessing each type of relevant liquidity resource at least annually.” 
                    <SU>40</SU>
                    <FTREF/>
                     The Liquidity Plan provides that CaLM undertakes “War Games” testing to ensure that assumptions around activities used in stressed environments to raise liquidity are realistic. The testing activities fall into three categories: (i) activities carried out under business as usual, such as the sale of securities, which demonstrate execution procedures and identify which counterparties have appetite; (ii) activities not relied on in day-to-day liquidity management but tested to demonstrate access to liquidity, such as repo transactions and access to Central Bank facilities, which are tested in relatively small size to verify procedures for execution and demonstrate access as a source of liquidity; and (iii) activities that cannot be fully tested through execution but are tested through simulation, such as simulating the liquidation of a defaulting member's collateral portfolio by asking counterparties to show bid prices in a “what if” scenario. The Liquidity Plan further specifies that CaLM tests access to qualifying liquid resources with each liquidity provider, to the extent practicable, not less than annually. By requiring LCH SA to maintain and test with each liquidity provider its procedures and operational capacity for accessing relevant liquidity resources at least annually, the Liquidity Plan is consistent with Commission Rule 17ad-22(e)(7)(v).
                    <SU>41</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         17 CFR 240.17ad-22(e)(7)(v).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         17 CFR 240.17ad-22(e)(7)(v).
                    </P>
                </FTNT>
                <P>
                    Commission Rule 17ad-22(e)(7)(vi) requires a covered clearing agency to determine the amount and regularly test the sufficiency of its liquid resources to meet the minimum requirement under Rule 17ad-22(e)(7)(i), including at a minimum: daily liquidity stress testing; monthly comprehensive analyses of stress scenarios, models, and key parameters with adjustments as appropriate; more frequent analyses when markets are volatile, less liquid, or participant positions become more concentrated (or in other appropriate circumstances); and reporting results to decision makers (
                    <E T="03">e.g.,</E>
                     risk management committee or board) and using them to evaluate and adjust the liquidity risk framework.
                    <SU>42</SU>
                    <FTREF/>
                     The Liquidity Plan establishes that liquidity stress testing in LCH SA includes daily liquidity stress testing for Cover 2 default by currency, intraday Cover 2 default liquidity stress testing, at least a 5-day forward-looking Cover 2 default liquidity stress test, and additional stress scenarios following a Cover 2 default. The Liquidity Plan also includes liquidity reverse stress scenarios. In addition, the Liquidity Plan provides that Second Line CaLM Risk monitors, controls, and reports the liquidity risk of LCH SA to CaLM on a daily basis, sets the Liquidity Risk Limits, and conducts liquidity stress testing. Second Line CaLM Risk maintains and runs various different stress scenarios and monitors the largest stress loss against the legal entity capital and available liquidity resources. By requiring LCH SA to conduct daily 
                    <PRTPAGE P="42583"/>
                    liquidity stress testing, perform comprehensive analyses of stress testing scenarios and parameters, and report the results to appropriate decision makers, the Liquidity Plan is consistent with Commission Rule 17ad-22(e)(7)(vi).
                    <SU>43</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         17 CFR 240.17ad-22(e)(7)(vi).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         17 CFR 240.17ad-22(e)(7)(vi).
                    </P>
                </FTNT>
                <P>
                    Commission Rule 17ad-22(e)(7)(viii) requires a covered clearing agency to address “foreseeable liquidity shortfalls that would not be covered by the covered clearing agency's liquid resources and seek to avoid unwinding, revoking, or delaying the same-day settlement of payment obligations.” 
                    <SU>44</SU>
                    <FTREF/>
                     The Liquidity Plan sets out options to generate operational liquidity and to meet operational and default liquidity shortfalls. If an operational liquidity shortfall is not fully met with maturing transactions, CaLM has a range of options to generate liquidity, with the choice and prioritisation of use depending on timing and duration of liquidity requirements and market conditions. For short-term liquidity requirements, funding is likely to focus on ECB liquidity, repo, and other borrowing mechanisms. For longer-term or structural changes to the liquidity profile, recourse is likely to be to the sale of assets. The Liquidity Plan also sets out additional methods to retain liquidity within LCH SA, including increasing the substitution notice period, utilising intraday liquidity available at CSDs, prioritising the return of non-cash over cash collateral, applying caps on pledge amounts and non-Euro securities, imposing service level cash primary liquid resources requirements, and making extraordinary margin calls if the LCR falls below specified thresholds. By establishing procedures to address foreseeable liquidity shortfalls and methods to retain liquidity to avoid delays in same-day settlement of payment obligations, the Liquidity Plan is consistent with Commission Rule 17ad-22(e)(7)(viii).
                    <SU>45</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         17 CFR 240.17ad-22(e)(7)(viii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         17 CFR 240.17ad-22(e)(7)(viii).
                    </P>
                </FTNT>
                <P>
                    Commission Rule 17ad-22(e)(7)(ix) requires a covered clearing agency to describe “the covered clearing agency's process to replenish any liquid resources that the clearing agency may employ during a stress event.” 
                    <SU>46</SU>
                    <FTREF/>
                     The Liquidity Plan describes the mechanics for replenishment of cash following liquidity usage. The primary source of cash to mitigate any liquidity shortfall is cash margin collateral posted by members, together with ECB-eligible securities that can be converted into cash through Banque de France. During default management, LCH SA may need to make payments on behalf of the defaulter to cover variation margins, settlement obligations, and hedging costs. To complete settlement of cleared contracts during a default, LCH SA will source the required liquidity either from the pool of cash posted by members or by utilising bonds under the cleared contract or from the non-cash collateral pool to raise liquidity through the Banque de France 3G credit line or repo transactions. The bond acquired is then sold in the auction and the proceeds used to replenish liquidity. If the bond is sold at a lower value than the cash paid under the repo, the resulting mark-to-market loss is covered by the default waterfall. By describing LCH SA's process to replenish liquid resources employed during a stress event, the Liquidity Plan is consistent with Commission Rule 17ad-22(e)(7)(ix).
                    <SU>47</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         17 CFR 240.17ad-22(e)(7)(ix).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         17 CFR 240.17ad-22(e)(7)(ix).
                    </P>
                </FTNT>
                <P>
                    Finally, Commission Rule 17ad-22(e)(7)(x) requires a covered clearing agency to undertake “an analysis at least once a year that evaluates the feasibility of maintaining sufficient liquid resources at a minimum in all relevant currencies to effect same-day and, where appropriate, intraday and multiday settlement of payment obligations with a high degree of confidence under a wide range of foreseeable stress scenarios that includes, but is not limited to, the default of the two participant families that would potentially cause the largest aggregate payment obligation for the covered clearing agency in extreme but plausible market conditions.” 
                    <SU>48</SU>
                    <FTREF/>
                     As discussed above,
                    <SU>49</SU>
                    <FTREF/>
                     the Liquidity Plan establishes that LCH SA conducts daily liquidity stress testing for Cover 2 default by currency, which models the default of the two member groups with the largest liquidity requirement under extreme but plausible market conditions. The comprehensive stress testing framework also includes additional stress scenarios following a Cover 2 default, Euronext Clearing liquidity stress testing, and liquidity reverse stress scenarios.
                    <SU>50</SU>
                    <FTREF/>
                     This annual validation evaluates the liquidity risk framework and the feasibility of the liquidity resources maintained by LCH SA to meet its payment obligations under stress scenarios. By establishing a framework for ongoing liquidity stress testing that includes Cover 2 default scenarios and providing for annual validation of its liquidity risk models, the Liquidity Plan, together with the LRP, is consistent with Commission Rule 17ad-22(e)(7)(x).
                    <SU>51</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         17 CFR 240.17ad-22(e)(7)(x).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         
                        <E T="03">See</E>
                         Item 3(a), 
                        <E T="03">supra.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         In addition, LCH SA's Liquidity Risk Policy (“LRP”) provides that the models used to conduct liquidity stress testing should be reviewed at least on a quarterly basis, with findings reported to the Executive Risk Committee, and that the model is subject to annual validation by an independent Model Validation Team in accordance with LCH SA's Model Governance Validation and Review Policy.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         17 CFR 240.17ad-22(e)(7)(x).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Clearing Agency's Statement on Burden on Competition</HD>
                <P>
                    Section 17A(b)(3)(I) of the Act requires that the rules of a clearing agency not impose any burden on competition not necessary or appropriate in furtherance of the purposes of the Act.
                    <SU>52</SU>
                    <FTREF/>
                     LCH SA does not believe the Liquidity Plan would have any impact, or impose any burden, on competition. The Liquidity Plan does not address any competitive issue or have any significant impact on the competition among central counterparties. LCH SA operates an open access clearing model, and the Liquidity Plan will have no direct effect on this open access model, subject to LCH SA's regulatory requirements and clearing rules, provisions and overall governance process, including the clearing membership eligibility criteria and appropriate credit risk assessment.
                </P>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         15 U.S.C. 78q-1(b)(3)(I).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Clearing Agency's Statement on Comments on the Proposed Rule Change Received from Members, Participants or Others</HD>
                <P>Written comments relating to the Liquidity Plan have not been solicited or received. LCH SA will notify the Commission of any written comments received by LCH SA.</P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change</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 self-regulatory organization consents, the Commission will: (A) by order approve or disapprove such proposed rule change, or (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. 
                    <PRTPAGE P="42584"/>
                    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-regulations/self-regulatory-organization-rulemaking</E>
                    ); or
                </P>
                <P>
                    • Send an email to 
                    <E T="03">rule-comments@sec.gov.</E>
                     Please include file number SR-LCH SA-2026-004 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-LCH SA-2026-004. 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">http://www.sec.gov/rules-regulations/self-regulatory-organization-rulemaking</E>
                    ). Copies of such filing will be available for inspection and copying at the principal office of LCH SA and on LCH SA's website at 
                    <E T="03">http://www.lch.com/resources/rules-and-regulations/proposed-rule-changes-0.</E>
                </FP>
                <P>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.</P>
                <P>All submissions should refer to file number SR-LCH SA-2026-004 and should be submitted on or before July 30, 2026.</P>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>53</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>53</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13828 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Investment Company Act Release No. 36241; File No. 812-16037]</DEPDOC>
                <SUBJECT>Datum One Series Trust and Polar Capital LLP</SUBJECT>
                <DATE>July 6, 2026.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission (“Commission” or “SEC”).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <P>Notice of an application under section 6(c) of the Investment Company Act of 1940 (“Act”) for an exemption from sections 2(a)(32), 5(a)(1), 18(f)(1), 18(i), 22(d) and 22(e) of the Act and rule 22c-1 under the Act and under sections 6(c) and 17(b) of the Act for an exemption from sections 17(a)(1) and 17(a)(2) of the Act.</P>
                <PREAMHD>
                    <HD SOURCE="HED">Summary of Application:</HD>
                    <P>Applicants request an order (“Order”) that would permit a registered open-end management investment company to offer one class of exchange-traded shares that operates as an exchange-traded fund (an “ETF Class,” and such shares, “ETF Shares”) and one or more classes of shares that are not exchange-traded (each such class, a “Mutual Fund Class,” and such shares, “Mutual Fund Shares,” and each such fund, a “Multi-Class ETF Fund”). The Order would provide Multi-Class ETF Funds with two broad categories of relief: (i) the relief necessary to permit standard exchange-traded fund (“ETF”) operations consistent with Rule 6c-11 under the Act (“ETF Operational Relief”) and (ii) the relief necessary for a fund to offer an ETF Class and one or more Mutual Fund Classes (“ETF Class Relief”).</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Applicants:</HD>
                    <P>Datum One Series Trust and Polar Capital LLP.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Filing Dates:</HD>
                    <P>The application was filed on June 5, 2026.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Hearing or Notification of Hearing:</HD>
                    <P>
                        An order granting the requested relief will be issued unless the Commission orders a hearing. Interested persons may request a hearing on any application by emailing the SEC's Secretary at 
                        <E T="03">Secretarys-Office@sec.gov</E>
                         and serving the Applicants with a copy of the request by email, if an email address is listed for the relevant Applicant below, or personally or by mail, if a physical address is listed for the relevant Applicant below. The email should include the file number referenced above. Hearing requests should be received by the Commission by 5:30 p.m., Eastern time, on July 31, 2026, and should be accompanied by proof of service on the Applicants, in the form of an affidavit or, for lawyers, a certificate of service. Pursuant to rule  0-5 under the Act, hearing requests should state the nature of the writer's interest, any facts bearing upon the desirability of a hearing on the matter, the reason for the request, and the issues contested. Persons who wish to be notified of a hearing may request notification by emailing the Commission's Secretary at 
                        <E T="03">Secretarys-Office@sec.gov.</E>
                    </P>
                </PREAMHD>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Commission: 
                        <E T="03">Secretarys-Office@sec.gov.</E>
                         Applicants: Barbara K. Nelligan, The Northern Trust Company, 50 S LaSalle Street, Chicago, Illinois 60603; Jessica Reece, Esq., Ropes &amp; Gray LLP, 
                        <E T="03">jessica.reece@ropesgray.com,</E>
                         800 Boylston Street, Boston, Massachusetts 02199.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Toyin Momoh, Senior Counsel, or Thomas Ahmadifar, Branch Chief, at (202) 551-6825 (Division of Investment Management, Chief Counsel's Office).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>For Applicants' representations, legal analysis, and conditions, please refer to Applicants' application, filed June 5, 2026, which may be obtained via the Commission's website by searching for the file number at the top of this document, or for an Applicant using the Company name search field, on the SEC's EDGAR system.</P>
                <P>
                    The SEC's EDGAR system may be searched at 
                    <E T="03">https://www.sec.gov/search-filings.</E>
                     You may also call the SEC's Office of Investor Education and Assistance at (202) 551-8090.
                </P>
                <SIG>
                    <P>For the Commission, by the Division of Investment Management, under delegated authority.</P>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13824 Filed 7-8-26; 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-105847; File No. SR-MX2-2026-03]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; MX2 LLC; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Amend Rule 2.13, Application Process and Waive-In</SUBJECT>
                <DATE>July 6, 2026.</DATE>
                <P>
                    Pursuant to the provisions of Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act” or “Exchange Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on June 30, 2026, MX2 LLC (“MX2” or the “Exchange”) 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 Exchange filed the proposal as a “non-controversial” proposed rule change pursuant to Section 
                    <PRTPAGE P="42585"/>
                    19(b)(3)(A)(iii) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 19b-4(f)(6) thereunder.
                    <SU>4</SU>
                    <FTREF/>
                     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>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</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 is filing with the Commission a proposed rule change to amend Exchange Rule 2.13 (Application Process and Waive-In) to make the Exchange's waive-in membership application process available on an ongoing basis to eligible applicants. The text of the proposed rule change is provided in Exhibit 5 and is available on the Exchange's website at 
                    <E T="03">https://info.memxtrading.com/regulation/rules-and-filings/.</E>
                </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 amend Rule 2.13 to remove the current limitation that makes the Exchange's waive-in membership application process available only during a temporary period beginning on the date the Exchange is approved by the Commission as a national securities exchange and ending 90 days after that date. The Commission approved MX2 as a national securities exchange on March 13, 2025,
                    <SU>5</SU>
                    <FTREF/>
                     and, accordingly, the 90-day waive-in period has already occurred and expired. However, MX2 has not yet commenced operations and is currently scheduled to launch its first trading facility, MX2 Options, on September 14, 2026. As such, the Exchange has not yet begun processing or approving any membership applications, and no applicant has been able to use or rely on the existing waive-in process. The proposal therefore would make the waive-in process available prospectively to all eligible applicants on an ongoing basis.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 102650 (March 13, 2025) 90 FR 12590 (March 18, 2025) (File No.10-247) (order approving application of MX2 LLC for registration as a national securities exchange).
                    </P>
                </FTNT>
                <P>
                    As amended, Rule 2.13 would permit an applicant that is: (i) a current member of MEMX LLC (“MEMX”); and (ii) an active member of FINRA or a registered national securities exchange other than MEMX, to apply to become a Member by submitting a waive-in application form prescribed by the Exchange, including agreements conforming with Rule 2.6(a)(1) through (a)(6).
                    <SU>6</SU>
                    <FTREF/>
                     The Exchange would continue to be able to request additional documentation to determine whether the applicant satisfies the qualification standards set forth in Rule 2.5.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         In connection with this proposed rule change, the Exchange would amend its Waive-In Membership Application Form to remove the reference to a 90-day waive-in period.
                    </P>
                </FTNT>
                <P>
                    The waive-in process recognizes that eligible applicants already have undergone self-regulatory organization (“SRO”) membership review and have an existing membership relationship with an affiliated national securities exchange. The process allows the Exchange to tailor its application review to information needed to determine whether an applicant satisfies the Exchange's membership requirements, without requiring duplicative submissions that are unnecessary in light of the applicant's existing SRO membership status. The Exchange believes the same considerations apply after its approval as a national securities exchange and on an ongoing basis. The Exchange notes that the rules of The Nasdaq Stock Market LLC (“Nasdaq”) contain similar waive-in application procedures pursuant to which eligible applicants may obtain exchange membership based on existing FINRA membership or membership with an affiliated exchange.
                    <SU>7</SU>
                    <FTREF/>
                     Like the proposed rule change, Nasdaq's waive-in procedures are available on an ongoing basis and are not limited to an initial post-approval or launch period.
                    <SU>8</SU>
                    <FTREF/>
                     The Exchange believes that the proposal is consistent with this existing Commission-approved approach to streamlined exchange membership applications for firms that are already subject to SRO oversight.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Nasdaq Rule 1013(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>The proposal would not provide for automatic membership approval or waive any substantive membership standard. Eligible applicants would still be required to submit the prescribed waive-in application form and required agreements; the Exchange would continue to review each applicant for compliance with Rule 2.5 and other applicable requirements; and the Exchange would retain discretion to request additional documentation. Accordingly, the proposal is administrative in nature and is designed to reduce unnecessary duplication without diminishing the Exchange's regulatory review or oversight of prospective Members.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes that its proposal is consistent with Section 6(b) of the Act,
                    <SU>9</SU>
                    <FTREF/>
                     in general, and furthers the objectives of Section 6(b)(5) of the Act,
                    <SU>10</SU>
                    <FTREF/>
                     in particular, in that it is designed to prevent fraudulent and manipulative 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. The Exchange also believes that the proposal is consistent with Section 6(b)(5) because it is not designed to permit unfair discrimination between customers, issuers, brokers, or dealers.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>The proposal would remove impediments to and perfect the mechanism of a free and open market and a national market system by making an existing streamlined membership application process available on an ongoing basis to a defined category of applicants that already are subject to SRO membership oversight. The current 90-day limitation is an administrative timing condition that does not affect whether an eligible applicant can satisfy the Exchange's substantive membership standards. Removing that limitation would allow the Exchange to process similarly situated applicants consistently regardless of when they seek membership.</P>
                <P>
                    The proposal also would protect investors and the public interest because it would not diminish the Exchange's ability to review prospective Members. Eligible applicants would remain subject to Rule 2.5, would be required to submit the prescribed waive-in application form and agreements conforming with Rule 2.6(a)(1) through (a)(6), and would be required to provide 
                    <PRTPAGE P="42586"/>
                    additional documentation if requested by the Exchange.
                </P>
                <P>
                    The Exchange also believes that the proposal is consistent with the Act because it aligns the Exchange's membership framework with an existing Commission-approved approach adopted by another national securities exchange.
                    <SU>11</SU>
                    <FTREF/>
                     The Exchange believes that adopting a similar ongoing waive-in process is a reasonable and appropriate means of facilitating efficient membership applications while preserving the Exchange's authority to evaluate whether applicants satisfy all applicable membership qualification standards.
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See supra</E>
                         note 7.
                    </P>
                </FTNT>
                <P>The proposal is not unfairly discriminatory because the waive-in process would remain available only to applicants satisfying objective eligibility criteria: current membership in MEMX and active membership in FINRA or another registered national securities exchange other than MEMX. Those criteria are reasonably related to the purpose of the waive-in process because such applicants already have undergone membership review and are subject to ongoing SRO oversight. Applicants that do not satisfy those criteria may continue to apply through the Exchange's standard membership application process.</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.</P>
                <P>The proposal would not impose an intramarket burden on competition because the waive-in process would be available on the same terms to all applicants that satisfy the objective eligibility criteria in Rule 2.13, and all other applicants could continue to apply through the Exchange's standard application process. The proposal also would not impose an intermarket burden on competition. To the extent it facilitates efficient access to the Exchange by qualified firms already subject to SRO oversight, the proposal may enhance competition among trading venues without restricting access to other markets.</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)(iii) 
                    <SU>12</SU>
                    <FTREF/>
                     of the Act and Rule 19b-4(f)(6) thereunder 
                    <SU>13</SU>
                    <FTREF/>
                     in that it effects a change that: (i) does not significantly affect the protection of investors or the public interest; (ii) does not impose any significant burden on competition; and (iii) by its terms, does not become operative for 30 days after the date of the filing, or such shorter time as the Commission may designate if consistent with the protection of investors and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78s(b)(3)(A)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <P>The proposed rule change does not significantly affect the protection of investors or the public interest because it does not alter any substantive standard applicable to Exchange membership. The proposal would remove only the temporary 90-day availability period applicable to the Exchange's waive-in membership application process. Eligible applicants would remain subject to the qualification standards set forth in Rule 2.5, would continue to be required to submit the prescribed waive-in application form and agreements conforming with Rule 2.6(a)(1) through (a)(6), and would remain subject to the Exchange's authority to request additional documentation as necessary to determine whether the applicant satisfies applicable membership requirements.</P>
                <P>The proposed rule change is also appropriately designated as non-controversial because it affects only the administration of the Exchange's membership application process and does not modify any substantive requirement for Exchange membership or otherwise affect the Exchange's regulatory oversight of Members. In addition, because MX2 has not commenced operations and has not yet begun processing or approving membership applications, no applicant has relied on the existing 90-day limitation in Rule 2.13.</P>
                <P>The proposed rule change also does not impose any significant burden on competition. The proposal would make the waive-in process available on the same terms to all applicants satisfying the objective eligibility criteria set forth in Rule 2.13 and would not alter the substantive qualifications for Exchange membership. To the extent the proposal facilitates efficient access to the Exchange by firms already subject to SRO oversight, it may enhance competition among trading venues.</P>
                <P>
                    Furthermore, the proposal is consistent with an existing Commission-approved approach to streamlined exchange membership applications. Nasdaq Rule 1013(b) contains ongoing waive-in application procedures for applicants that already are subject to SRO oversight through existing FINRA membership or membership in an affiliated exchange. The proposal would adopt a comparable ongoing waive-in process for MX2 and therefore does not present any novel regulatory issues that would warrant treatment other than pursuant to Rule 19b-4(f)(6).
                    <SU>14</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         17 CFR 240.19b-4(f)(6).
                    </P>
                </FTNT>
                <P>
                    Furthermore, Rule 19b-4(f)(6)(iii) 
                    <SU>15</SU>
                    <FTREF/>
                     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. 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: (i) necessary or appropriate in the public interest; (ii) for the protection of investors; or (iii) otherwise in furtherance of the purposes of the Act. If the Commission takes such action, the Commission shall institute proceedings to determine whether the proposed rule should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         17 CFR 240.19b-4(f)(6)(iii).
                    </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-MX2-2026-03 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-MX2-2026-03. This file number should be included on the subject line if email is used. To help the 
                    <PRTPAGE P="42587"/>
                    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 filing 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-MX2-2026-03 and should be submitted on or before July 30, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>16</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13826 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[OMB Control No. 3235-0195]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Proposed Collection; Comment Request; Extension: Rule 17Ab2-1 and Form CA-1</SUBJECT>
                <FP SOURCE="FP-1">
                    <E T="03">Upon Written Request, Copies Available From:</E>
                     Securities and Exchange Commission, Office of FOIA Services, 100 F Street NE, Washington, DC 20549-2736
                </FP>
                <P>
                    Notice is hereby given that, pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the Securities and Exchange Commission (“SEC” or “Commission”) is soliciting comments on the collection of information provided for in Rule 17Ab2-1 (17 CFR 240.17Ab2-1) and Form CA-1: Registration of Clearing Agencies (17 CFR 249b.200) under the Securities Exchange Act of 1934 (“Exchange Act”) (15 U.S.C. 78a 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <P>Rule 17Ab2-1 and Form CA-1 require clearing agencies to register with the Commission and to meet certain requirements with regard to, among other things, the clearing agency's organization, capacities, and rules. The information is collected from the clearing agency upon the initial application for registration on Form CA-1. Thereafter, information is collected by amendment to the initial Form CA-1 when changes in circumstances that render certain information on Form CA-1 inaccurate, misleading, or incomplete necessitate modification of the information previously provided to the Commission.</P>
                <P>The Commission uses the information disclosed on Form CA-1 to: (1) determine whether an applicant meets the standards for registration set forth in Section 17A of the Exchange Act, (2) enforce compliance with the Exchange Act's registration requirement, and (3) provide information about specific registered clearing agencies for compliance and investigatory purposes. Without Rule 17Ab2-1, the Commission could not perform these duties as statutorily required.</P>
                <P>
                    The Commission staff estimates that the Commission receives approximately three new Form CA-1 applications, and approximately ten amendments to existing Forms CA-1, per year pursuant to Rule 17Ab2-1. Recently, Commission staff has seen an increase in the complexity and length of Form CA-1 applications received, likely due to new market developments such as cloud computing, cybersecurity, sponsored clearing, Distributed Ledger Technology, and Treasury clearing products. As such, the Commission staff estimates that the Form CA-1 would take approximately 651 hours to complete and submit for approval, and amending an existing Form CA-1 would take approximately 60 hours to complete and submit. Consequently, the aggregate annual burden associated with compliance with Rule 17Ab2-1 and Form CA-1 is approximately 2553 hours.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         (651 burden hours per applicant × 3 applicants) + (60 hours per amendment × 10 amendments).
                    </P>
                </FTNT>
                <P>
                    The Commission staff estimates that, in order to complete a new Form CA-1, 611 hours of a Lawyer's time (estimated at $744 per hour) 
                    <SU>2</SU>
                    <FTREF/>
                     and 40 hours of a Chief Executive's time (estimated at $999 per hour) would be required, resulting in an internal cost of compliance of approximately $494,544 for a new applicant.
                    <SU>3</SU>
                    <FTREF/>
                     For an amendment of an existing Form CA-1, the staff estimates that 40 hours of a Lawyer's time and 20 hours of a Chief Executive's time would be required, resulting in an internal cost of compliance of $49,740.
                    <SU>4</SU>
                    <FTREF/>
                     Therefore, the total annualized internal cost of compliance is estimated to be approximately $1,981,032.
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         For purposes of calculating the dollar cost burdens associated with applicants using Form CA-1, the Commission relies on the Occupational Employment and Wage Statistics (“OEWS”) from the U.S. Bureau of Labor Statistics (“BLS”). 
                        <E T="03">See Occupational Employment and Wage Classification,</E>
                         U.S. Bureau of Labor Statistics, 
                        <E T="03">https://www.bls.gov/oes/; see also Standard Occupational Classification,</E>
                         U.S. Bureau of Labor Statistics, 
                        <E T="03">https://www.bls.gov/soc/</E>
                         (describing occupational classification system used by BLS); Exec. Off. Of the President, Off. Of Mgmt. &amp; Budget, North American Industrial Classification System (2022), 
                        <E T="03">available at https://www.census.gov/naics/reference_files_tools/2022_NAICS_Manual.pdf</E>
                         (describing the industry adjusted for changes in the seasonally adjusted employment cost index for private wages and salaries between the data reference period and when the data are released by BLS. 
                        <E T="03">See Employment Cost Index, U.S. Bureau of Labor Statistics</E>
                        , 
                        <E T="03">https://www.bls.gov/eci/</E>
                        . The adjusted mean hourly wage is then multiplied by a factor that accounts for nonwage costs borne by employers, such as bonuses, benefits, and overhead. This factor is calculated as an average over the 10 most recently available years of data of the ratio of the Bureau of Economic Analysis's annual gross output data for the North American Industry Classification System (“NAICS”) number to total annual wages across all occupations for the NAICS number in the OEWS data.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         (611 burden hours for a lawyer per applicant × $744 per hour) + (40 burden hours for a Chief Executive per applicant × $999 per hour).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         (40 burden hours for a lawyer per amendment × $744 per hour) + (20 burden hours for a Chief Executive per amendment × $999 per hour).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         (3 respondents × $494,544 per application) + (10 respondents × $49,740 per amendment).
                    </P>
                </FTNT>
                <P>
                    The external costs associated with work on Form CA-1 include fees charged by outside lawyers and accountants to assist the applicant or registrant to collect and prepare the information sought by the form (though such consultations are not required by the Commission). The staff estimates that these external costs are more likely when novel questions arise. Recently, the staff has seen an increase in the number of novel issues presented in applications and amendments. The staff estimates an annual external cost of 60 hours of an external Lawyer's time (estimated at $498 per hour) and 10 hours of an external Accountant's time (estimated at $241 per hour) for preparation of a Form CA-1 application, resulting in an external cost of $32,290 per year per applicant, with an aggregate external cost of approximately $96,870 per year.
                    <SU>6</SU>
                    <FTREF/>
                     The staff estimates an annual external cost of 5 hours of an external Lawyer's time (estimated at $498 per hour) for preparation of a Form CA-1 amendment, resulting in an external cost of $2,490 per year per clearing agency, with an aggregate external cost of approximately $24,900 per year.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         (60 burden hours for a lawyer per applicant × 3 applications per year × $498 per hour) + (10 burden hours for an accountant per applicant × 3 applications per year × $241 per hour).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         5 burden hours for a lawyer per amendment × 10 amendments per year × $498 per hour.
                    </P>
                </FTNT>
                <P>An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB Control Number.</P>
                <P>
                    <E T="03">Written comments are invited on:</E>
                     (a) whether the proposed collection of information is necessary for the proper 
                    <PRTPAGE P="42588"/>
                    performance of the functions of the SEC, including whether the information will have practical utility; (b) the accuracy of the SEC's estimates of the burden imposed by the proposed collection of information, including the validity of the methodology and the assumptions used; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated, electronic collection techniques or other forms of information technology.
                </P>
                <P>
                    Please direct your written comments on this 60-Day Collection Notice to Austin Gerig, Director/Chief Data Officer, Securities and Exchange Commission, c/o Tanya Ruttenberg via email to 
                    <E T="03">PaperworkReductionAct@sec.gov</E>
                     by September 8, 2026.
                </P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13817 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Investment Company Act Release No. 36239; File No. 812-16036]</DEPDOC>
                <SUBJECT>Datum One Series Trust and Brandes Investment Partners, L.P.</SUBJECT>
                <DATE>July 6, 2026.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission (“Commission” or “SEC”).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <P>Notice of an application under section 6(c) of the Investment Company Act of 1940 (“Act”) for an exemption from sections 2(a)(32), 5(a)(1), 18(f)(1), 18(i), 22(d) and 22(e) of the Act and rule  22c-1 under the Act and under sections 6(c) and 17(b) of the Act for an exemption from sections 17(a)(1) and 17(a)(2) of the Act.</P>
                <PREAMHD>
                    <HD SOURCE="HED">Summary of Application:</HD>
                    <P>Applicants request an order (“Order”) that would permit a registered open-end management investment company to offer one class of exchange-traded shares that operates as an exchange-traded fund (an “ETF Class,” and such shares, “ETF Shares”) and one or more classes of shares that are not exchange-traded (each such class, a “Mutual Fund Class,” and such shares, “Mutual Fund Shares,” and each such fund, a “Multi-Class ETF Fund”). The Order would provide Multi-Class ETF Funds with two broad categories of relief: (i) the relief necessary to permit standard exchange-traded fund (“ETF”) operations consistent with Rule 6c-11 under the Act (“ETF Operational Relief”) and (ii) the relief necessary for a fund to offer an ETF Class and one or more Mutual Fund Classes (“ETF Class Relief”).</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Applicants:</HD>
                    <P>Datum One Series Trust and Brandes Investment Partners, L.P.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Filing Dates:</HD>
                    <P>The application was filed on June 5, 2026.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Hearing or Notification of Hearing:</HD>
                    <P>
                        An order granting the requested relief will be issued unless the Commission orders a hearing. Interested persons may request a hearing on any application by emailing the SEC's Secretary at 
                        <E T="03">Secretarys-Office@sec.gov</E>
                         and serving the Applicants with a copy of the request by email, if an email address is listed for the relevant Applicant below, or personally or by mail, if a physical address is listed for the relevant Applicant below. The email should include the file number referenced above. Hearing requests should be received by the Commission by 5:30 p.m., Eastern time, on July 31, 2026, and should be accompanied by proof of service on the Applicants, in the form of an affidavit or, for lawyers, a certificate of service. Pursuant to rule 0-5 under the Act, hearing requests should state the nature of the writer's interest, any facts bearing upon the desirability of a hearing on the matter, the reason for the request, and the issues contested. Persons who wish to be notified of a hearing may request notification by emailing the Commission's Secretary at 
                        <E T="03">Secretarys-Office@sec.gov.</E>
                    </P>
                </PREAMHD>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Commission: 
                        <E T="03">Secretarys-Office@sec.gov.</E>
                         Applicants: Barbara K. Nelligan, The Northern Trust Company, 50 S LaSalle Street, Chicago, Illinois 60603; Jessica Reece, Esq., Ropes &amp; Gray LLP, 
                        <E T="03">jessica.reece@ropesgray.com,</E>
                         800 Boylston Street, Boston, Massachusetts 02199.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Toyin Momoh, Senior Counsel, or Thomas Ahmadifar, Branch Chief, at (202) 551-6825 (Division of Investment Management, Chief Counsel's Office).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>For Applicants' representations, legal analysis, and conditions, please refer to Applicants' application, filed June 5, 2026, which may be obtained via the Commission's website by searching for the file number at the top of this document, or for an Applicant using the Company name search field, on the SEC's EDGAR system.</P>
                <P>
                    The SEC's EDGAR system may be searched at 
                    <E T="03">https://www.sec.gov/search-filings.</E>
                     You may also call the SEC's Office of Investor Education and Assistance at (202) 551-8090.
                </P>
                <SIG>
                    <P>For the Commission, by the Division of Investment Management, under delegated authority.</P>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13822 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Investment Company Act Release No. 36240; File No. 812-16044]</DEPDOC>
                <SUBJECT>Datum One Series Trust and First Sentier Investors (US) LLC</SUBJECT>
                <DATE>July 6, 2026.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission (“Commission” or “SEC”).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <P>Notice of an application under section 6(c) of the Investment Company Act of 1940 (“Act”) for an exemption from sections 2(a)(32), 5(a)(1), 18(f)(1), 18(i), 22(d) and 22(e) of the Act and rule 22c-1 under the Act and under sections 6(c) and 17(b) of the Act for an exemption from sections 17(a)(1) and 17(a)(2) of the Act.</P>
                <PREAMHD>
                    <HD SOURCE="HED">Summary of Application:</HD>
                    <P>Applicants request an order (“Order”) that would permit a registered open-end management investment company to offer one class of exchange-traded shares that operates as an exchange-traded fund (an “ETF Class,” and such shares, “ETF Shares”) and one or more classes of shares that are not exchange-traded (each such class, a “Mutual Fund Class,” and such shares, “Mutual Fund Shares,” and each such fund, a “Multi-Class ETF Fund”). The Order would provide Multi-Class ETF Funds with two broad categories of relief: (i) the relief necessary to permit standard exchange-traded fund (“ETF”) operations consistent with Rule 6c-11 under the Act (“ETF Operational Relief”) and (ii) the relief necessary for a fund to offer an ETF Class and one or more Mutual Fund Classes (“ETF Class Relief”).</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Applicants:</HD>
                    <P>Datum One Series Trust and First Sentier Investors (US) LLC.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Filing Dates:</HD>
                    <P>The application was filed on June 12, 2026.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Hearing or Notification of Hearing:</HD>
                    <P>
                        An order granting the requested relief will be issued unless the Commission orders a hearing. Interested persons may request a hearing on any application by emailing the SEC's Secretary at 
                        <E T="03">Secretarys-Office@sec.gov</E>
                         and serving the Applicants with a copy of the request by email, if an email address is listed for the relevant Applicant below, 
                        <PRTPAGE P="42589"/>
                        or personally or by mail, if a physical address is listed for the relevant Applicant below. The email should include the file number referenced above. Hearing requests should be received by the Commission by 5:30 p.m., Eastern time, on July 31, 2026, and should be accompanied by proof of service on the Applicants, in the form of an affidavit or, for lawyers, a certificate of service. Pursuant to rule 0-5 under the Act, hearing requests should state the nature of the writer's interest, any facts bearing upon the desirability of a hearing on the matter, the reason for the request, and the issues contested. Persons who wish to be notified of a hearing may request notification by emailing the Commission's Secretary at 
                        <E T="03">Secretarys-Office@sec.gov.</E>
                    </P>
                </PREAMHD>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Commission: 
                        <E T="03">Secretarys-Office@sec.gov.</E>
                         Applicants: Barbara K. Nelligan, The Northern Trust Company, 50 S LaSalle Street, Chicago, Illinois 60603; Jessica Reece, Esq., Ropes &amp; Gray LLP, 
                        <E T="03">jessica.reece@ropesgray.com,</E>
                         800 Boylston Street, Boston, Massachusetts 02199.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Toyin Momoh, Senior Counsel, or Thomas Ahmadifar, Branch Chief, at (202) 551-6825 (Division of Investment Management, Chief Counsel's Office).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>For Applicants' representations, legal analysis, and conditions, please refer to Applicants' application, filed June 12, 2026, which may be obtained via the Commission's website by searching for the file number at the top of this document, or for an Applicant using the Company name search field, on the SEC's EDGAR system.</P>
                <P>
                    The SEC's EDGAR system may be searched at 
                    <E T="03">https://www.sec.gov/search-filings.</E>
                     You may also call the SEC's Office of Investor Education and Assistance at (202) 551-8090.
                </P>
                <SIG>
                    <P>For the Commission, by the Division of Investment Management, under delegated authority.</P>
                    <NAME>Sherry R. Haywood,</NAME>
                    <TITLE>Assistant Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13823 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <SUBJECT>Fiscal Year List of Requests From States or Tribes for a Small Business Administration Disaster Declaration</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice provides an updated monthly summary of requests received by the U. S. Small Business Administration to make a disaster declaration for a state, territory, or tribe. The published list complies with a directive in the explanatory statement of the Consolidated Appropriations Act, 2026, Public Law 119-75.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Issued on July 7, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>For further information contact: Eric Wall, Office of Disaster Recovery and Resilience, U.S. Small Business Administration, 409 3rd Street SW, Suite 6050, Washington, DC 20416, (202) 205-6739.</P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given as of June 30, 2026, the following requests have been made to the U.S. Small Business Administration in Fiscal Year 2026 to declare a disaster.</P>
                <GPOTABLE COLS="6" OPTS="L2,nj,tp0,p7,7/8,i1" CDEF="s25,r50,r75,r40,r25,r40">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">State</CHED>
                        <CHED H="1">Disaster date(s)</CHED>
                        <CHED H="1">Disaster description</CHED>
                        <CHED H="1">
                            Date of state
                            <LI>request to SBA</LI>
                        </CHED>
                        <CHED H="1">
                            Approval
                            <LI>status</LI>
                        </CHED>
                        <CHED H="1">Date of declaration</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Arizona</ENT>
                        <ENT>September 25-27, 2025</ENT>
                        <ENT>Gila County Flooding Event</ENT>
                        <ENT>October 9, 2025</ENT>
                        <ENT>Approved</ENT>
                        <ENT>October 10, 2025.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Illinois</ENT>
                        <ENT>July 10-August 1, 2025</ENT>
                        <ENT>Algal Bloom Water Contamination</ENT>
                        <ENT>November 4, 2025</ENT>
                        <ENT>Approved</ENT>
                        <ENT>November 6, 2025.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arizona</ENT>
                        <ENT>October 10-13, 2025</ENT>
                        <ENT>Remnants of Hurricane Priscilla and Tropical Storm Raymond</ENT>
                        <ENT>November 4, 2025</ENT>
                        <ENT>Approved</ENT>
                        <ENT>November 14, 2025.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Florida</ENT>
                        <ENT>October 26, 2025</ENT>
                        <ENT>Severe Storms and Flooding</ENT>
                        <ENT>November 7, 2025</ENT>
                        <ENT>Approved</ENT>
                        <ENT>November 7, 2025.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New York</ENT>
                        <ENT>September 17, 2025</ENT>
                        <ENT>Red Hook Five-Alarm Fire</ENT>
                        <ENT>November 13, 2025</ENT>
                        <ENT>Approved</ENT>
                        <ENT>November 14, 2025.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Kentucky</ENT>
                        <ENT>November 4, 2025</ENT>
                        <ENT>Louisville Airplane Crash</ENT>
                        <ENT>November 14, 2025</ENT>
                        <ENT>Approved</ENT>
                        <ENT>November 15, 2025.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Colorado</ENT>
                        <ENT>August 2-29, 2025</ENT>
                        <ENT>Lee and Elk Fires, Mudslides, and Debris Flows</ENT>
                        <ENT>November 17, 2025</ENT>
                        <ENT>Approved</ENT>
                        <ENT>November 18, 2025.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">California</ENT>
                        <ENT>November 13-December 4, 2025</ENT>
                        <ENT>Pack Fire</ENT>
                        <ENT>December 4, 2025</ENT>
                        <ENT>Approved</ENT>
                        <ENT>December 9, 2025.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New York</ENT>
                        <ENT>November 23, 2025</ENT>
                        <ENT>Cottage Avenue Apartment Building Fire</ENT>
                        <ENT>December 12, 2025</ENT>
                        <ENT>Approved</ENT>
                        <ENT>December 16, 2025.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Minnesota</ENT>
                        <ENT>October 26, 2025</ENT>
                        <ENT>Skyline Tower Apartment Complex Fire and Severe Water Damage</ENT>
                        <ENT>December 19, 2025</ENT>
                        <ENT>Approved</ENT>
                        <ENT>December 22, 2025.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">California</ENT>
                        <ENT>December 16-26, 2025</ENT>
                        <ENT>2025 Late December Storm</ENT>
                        <ENT>January 28, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>February 3, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">California</ENT>
                        <ENT>December 31, 2025-January 5, 2026</ENT>
                        <ENT>2026 Early January Storm, Tidal Flooding, and King Tides</ENT>
                        <ENT>January 28, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>February 3, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Louisiana</ENT>
                        <ENT>January 23-27, 2026</ENT>
                        <ENT>2026 Severe Winter Storm</ENT>
                        <ENT>January 30, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>February 2, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">California</ENT>
                        <ENT>December 16-26, 2025</ENT>
                        <ENT>2025 Late December Storms</ENT>
                        <ENT>January 30, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>February 6, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">California</ENT>
                        <ENT>January 19, 2026</ENT>
                        <ENT>Oakland Apartment Fire</ENT>
                        <ENT>February 4, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>February 10, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Washington</ENT>
                        <ENT>December 5-22, 2025</ENT>
                        <ENT>Severe Winter Storms, 2025</ENT>
                        <ENT>February 11, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>February 24, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New Mexico</ENT>
                        <ENT>June 23-August 5, 2025</ENT>
                        <ENT>Mescalero Apache Tribe—Rural Area—Severe Storms, Flooding and Landslides</ENT>
                        <ENT>February 17, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>February 23, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pennsylvania</ENT>
                        <ENT>February 20, 2026</ENT>
                        <ENT>Hotel Hampton Fire</ENT>
                        <ENT>March 3, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>March 4, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Illinois</ENT>
                        <ENT>August 16-19, 2025</ENT>
                        <ENT>Severe Storms, Straight-Line Winds, and Flash Flooding</ENT>
                        <ENT>March 12, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>March 16, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tennessee</ENT>
                        <ENT>January 22-27, 2026</ENT>
                        <ENT>2026 Severe Winter Storm Fern</ENT>
                        <ENT>March 23, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>April 7, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Hawaii</ENT>
                        <ENT>November 30, 2025</ENT>
                        <ENT>Downtown Hilo Fire</ENT>
                        <ENT>April 1, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>April 3, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Louisiana</ENT>
                        <ENT>January 23-27, 2026</ENT>
                        <ENT>Louisiana Severe Winter Storm</ENT>
                        <ENT>April 2, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>April 8, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Illinois</ENT>
                        <ENT>March 10, 2026</ENT>
                        <ENT>Severe Storm and Tornado</ENT>
                        <ENT>April 7, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>April 9, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Indiana</ENT>
                        <ENT>March 10-11, 2026</ENT>
                        <ENT>Severe Storms and Tornado</ENT>
                        <ENT>April 7, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>April 9, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Alaska</ENT>
                        <ENT>October 8-13, 2025</ENT>
                        <ENT>Severe Storms, Flooding and Remnants of Typhoon Halong</ENT>
                        <ENT>April 13, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>April 15, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arkansas</ENT>
                        <ENT>January 23-26, 2026</ENT>
                        <ENT>Severe Winter Weather</ENT>
                        <ENT>April 14, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>April 29, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Illinois</ENT>
                        <ENT>July 25-28, 2025</ENT>
                        <ENT>Severe Storms and Flash Flooding</ENT>
                        <ENT>April 22, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>April 23, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Michigan</ENT>
                        <ENT>March 6, 2026</ENT>
                        <ENT>Tornadoes</ENT>
                        <ENT>April 27, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>April 28, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Oklahoma</ENT>
                        <ENT>April 2, 2026</ENT>
                        <ENT>Severe Weather, Tornadoes, and Straight-line Winds</ENT>
                        <ENT>May 1, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>May 1, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Texas</ENT>
                        <ENT>April 24-May 1, 2026</ENT>
                        <ENT>Severe Storms and Tornadoes</ENT>
                        <ENT>May 5, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>May 7, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Illinois</ENT>
                        <ENT>April 17, 2026</ENT>
                        <ENT>Severe Storm and Tornado</ENT>
                        <ENT>May 15, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>May 18, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Georgia</ENT>
                        <ENT>April 20, 2026</ENT>
                        <ENT>Wildfires</ENT>
                        <ENT>May 26, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>May 27, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Idaho</ENT>
                        <ENT>December 16-18, 2025</ENT>
                        <ENT>Straight-line Winds</ENT>
                        <ENT>June 3, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>June 8, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="42590"/>
                        <ENT I="01">Oregon</ENT>
                        <ENT>December 15-21, 2025</ENT>
                        <ENT>Severe Storms, Straight-line Winds, Flooding, Landslides, and Mudslides</ENT>
                        <ENT>June 2, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>June 4, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rhode Island</ENT>
                        <ENT>February 22-23, 2026</ENT>
                        <ENT>2026 Historic Snowstorm</ENT>
                        <ENT>June 3, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>June 10, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Illinois</ENT>
                        <ENT>May 15, 2026</ENT>
                        <ENT>Oak Lawn Apartment Complex Fire</ENT>
                        <ENT>June 9, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>June 10, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">California</ENT>
                        <ENT>May 21-29, 2026</ENT>
                        <ENT>Garden Grove Hazmat Incident</ENT>
                        <ENT>June 8, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>June 11, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Massachusetts</ENT>
                        <ENT>February 22-27, 2026</ENT>
                        <ENT>Blizzard</ENT>
                        <ENT>June 8, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>June 12, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New Jersey</ENT>
                        <ENT>May 3-14, 2026</ENT>
                        <ENT>12-Alarm Warehouse Fire</ENT>
                        <ENT>June 10, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>June 12, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pennsylvania</ENT>
                        <ENT>June 11, 2026</ENT>
                        <ENT>Oak Forest Apartment Complex Fire</ENT>
                        <ENT>June 23, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>June 24, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New York</ENT>
                        <ENT>May 20, 026</ENT>
                        <ENT>Severe Storms and Flooding</ENT>
                        <ENT>June 26, 2026</ENT>
                        <ENT>Approved</ENT>
                        <ENT>June 30, 2026.</ENT>
                    </ROW>
                </GPOTABLE>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Number 59008)</FP>
                </EXTRACT>
                <P>
                    <E T="03">Authority:</E>
                     13 CFR 123.3(b).
                </P>
                <SIG>
                    <NAME>James Stallings,</NAME>
                    <TITLE>Associate Administrator, Office of Disaster Recovery &amp; Resilience.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13866 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8026-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #21664 and #21665; MISSISSIPPI Disaster Number MS-20020]</DEPDOC>
                <SUBJECT>Presidential Declaration of a Major Disaster for the State of Mississippi</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is notice of the Presidential declaration of a major disaster for the State of Mississippi (FEMA-4922- DR), dated June 30, 2026.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms, Straight-line Winds, Tornadoes, and Flooding.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Issued on June 30, 2026.</P>
                    <P>
                        <E T="03">Incident Period:</E>
                         May 6, 2026 through May 7, 2026.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         August 31, 2026.
                    </P>
                    <P>
                        <E T="03">Economic Injury (EIDL) Loan Application Deadline Date:</E>
                         March 30, 2027.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        <E T="03">Visit the MySBA Loan Portal at https://lending.sba.gov</E>
                         to apply for a disaster assistance loan.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sharon Henderson, Office of Disaster Recovery and Resilience, U.S. Small Business Administration, 409 3rd Street SW, Suite 6050, Washington, DC 20416, (202) 205-6734.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given as a result of the President's major disaster declaration on June 30, 2026, applications for disaster loans may be submitted online using the MySBA Loan Portal 
                    <E T="03">https://lending.sba.gov</E>
                     or in person at other locally announced locations. For further assistance please contact the SBA disaster assistance customer service center by email at 
                    <E T="03">disastercustomerservice@sba.gov</E>
                     or by phone at 1-800-659-2955. If you are deaf, hard of hearing or have a speech disability, please dial 7-1-1 to access telecommunications relay services.
                </P>
                <P>The following areas have been determined to be adversely affected by the disaster:</P>
                <FP SOURCE="FP-2">
                    <E T="03">Primary Counties (Physical Damage and Economic Injury Loans):</E>
                     Franklin, Lamar, Lawrence, Lincoln, Wilkinson.
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">Contiguous Counties/Parishes (Economic Injury Loans Only):</E>
                </FP>
                <FP SOURCE="FP1-2">Mississippi: Adams, Amite, Copiah, Covington, Forrest, Jefferson, Jefferson Davis, Marion, Pearl River, Pike, Simpson, Walthall.</FP>
                <FP SOURCE="FP1-2">Louisiana: Concordia, East Feliciana, West Feliciana.</FP>
                <P>The Interest Rates are:</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s50,8">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">Percent</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">
                            <E T="03">For Physical Damage:</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Homeowners with Credit Available Elsewhere </ENT>
                        <ENT>5.750</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Homeowners without Credit Available Elsewhere </ENT>
                        <ENT>2.875</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Businesses with Credit Available Elsewhere </ENT>
                        <ENT>8.000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Businesses without Credit Available Elsewhere </ENT>
                        <ENT>4.000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Private Non-Profit Organizations with Credit Available Elsewhere </ENT>
                        <ENT>3.625</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Private Non-Profit Organizations without Credit Available Elsewhere </ENT>
                        <ENT>3.625</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            <E T="03">For Economic Injury:</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Business and Small Agricultural Cooperatives without Credit Available Elsewhere </ENT>
                        <ENT>4.000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Private Non-Profit Organizations without Credit Available Elsewhere </ENT>
                        <ENT>3.625</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The number assigned to this disaster for physical damage is 216646 and for economic injury is 216650.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Number 59008)</FP>
                    <FP>(Authority: 13 CFR 123.3(b).)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>James Stallings,</NAME>
                    <TITLE>Associate Administrator, Office of Disaster Recovery &amp; Resilience.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13853 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8026-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #21658 and #21659; WISCONSIN Disaster Number WI-20005]</DEPDOC>
                <SUBJECT>Presidential Declaration of a Major Disaster for the State of Wisconsin</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Small Business Administration.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is notice of the Presidential declaration of a major disaster for the State of Wisconsin (FEMA-4923- DR), dated June 30, 2026.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Severe Storms, Tornadoes, and Flooding.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Issued on June 30, 2026.</P>
                    <P>
                        <E T="03">Incident Period:</E>
                         April 13, 2026 through April 23, 2026.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         August 31, 2026.
                    </P>
                    <P>
                        <E T="03">Economic Injury (EIDL) Loan Application Deadline Date:</E>
                         March 30, 2027.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        <E T="03">Visit the MySBA Loan Portal at https://lending.sba.gov</E>
                         to apply for a disaster assistance loan.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jennifer Talarico, Office of Disaster Recovery and Resilience, U.S. Small Business Administration, 409 3rd Street SW, Suite 6050, Washington, DC 20416, (202) 205-6734.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Notice is hereby given as a result of the President's major disaster declaration on June 30, 2026, applications for disaster loans may be submitted online using the MySBA Loan Portal 
                    <E T="03">https://lending.sba.gov</E>
                     or in person at other locally announced locations. For further assistance please contact the SBA disaster assistance customer service center by email at 
                    <E T="03">disastercustomerservice@sba.gov</E>
                     or by phone at 1-800-659-2955. If you are deaf, hard of hearing or have a speech disability, please dial 7-1-1 to access telecommunications relay services.
                </P>
                <P>The following areas have been determined to be adversely affected by the disaster:</P>
                <FP SOURCE="FP-2">
                    <E T="03">Primary Counties (Physical Damage and Economic Injury Loans):</E>
                     Bayfield, Brown, Buffalo, Jackson, Jefferson, 
                    <PRTPAGE P="42591"/>
                    Juneau, Kenosha, Manitowoc, Marathon, Milwaukee, Outagamie, Racine, Rock, Sauk, Vernon, Washington, Waukesha, Waupaca, Winnebago.
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">Tribal Areas:</E>
                     Oneida Nation.
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">Contiguous Counties (Economic Injury Loans Only):</E>
                </FP>
                <FP SOURCE="FP1-2">Wisconsin: Adams, Ashland, Calumet, Clark, Columbia, Crawford, Dane, Dodge, Douglas, Eau Claire, Fond du Lac, Green, Green Lake, Iowa, Kewaunee, La Crosse, Langlade, Lincoln, Monroe, Oconto, Ozaukee, Pepin, Portage, Richland, Sawyer, Shawano, Sheboygan, Taylor, Trempealeau, Walworth, Washburn, Waushara, Wood.</FP>
                <FP SOURCE="FP1-2">Iowa: Allamakee.</FP>
                <FP SOURCE="FP1-2">Illinois: Boone, Lake, McHenry, Winnebago.</FP>
                <FP SOURCE="FP1-2">Minnesota: Houston, Wabasha, Winona.</FP>
                <P>The Interest Rates are:</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,i1" CDEF="s50,8">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">Percent</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">
                            <E T="03">For Physical Damage:</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Homeowners with Credit Available Elsewhere </ENT>
                        <ENT>5.750</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Homeowners without Credit Available Elsewhere </ENT>
                        <ENT>2.875</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Businesses with Credit Available Elsewhere </ENT>
                        <ENT>8.000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Businesses without Credit Available Elsewhere </ENT>
                        <ENT>4.000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Private Non-Profit Organizations with Credit Available Elsewhere </ENT>
                        <ENT>3.625</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Private Non-Profit Organizations without Credit Available Elsewhere </ENT>
                        <ENT>3.625</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            <E T="03">For Economic Injury:</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Business and Small Agricultural Cooperatives without Credit Available Elsewhere </ENT>
                        <ENT>4.000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Private Non-Profit Organizations without Credit Available Elsewhere </ENT>
                        <ENT>3.625</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The number assigned to this disaster for physical damage is 216586 and for economic injury is 216590.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Number 59008)</FP>
                    <FP>(Authority: 13 CFR 123.3(b).)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>James Stallings,</NAME>
                    <TITLE>Associate Administrator, Office of Disaster Recovery &amp; Resilience.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13854 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8026-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Highway Administration</SUBAGY>
                <DEPDOC>[Docket No. FHWA-2026-0826]</DEPDOC>
                <SUBJECT>Notice of Intent To Prepare an Environmental Impact Statement, Washington County, Maine</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Highway Administration (FHWA), U.S. Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Intent to prepare an environmental impact statement.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>FHWA, on behalf of the Maine Department of Transportation (MaineDOT), is issuing this notice to advise the public that an Environmental Impact Statement (EIS) will be prepared for proposed transportation improvements to the Machias Dike Bridge (#2246) on U.S. Route 1 in Machias, Maine. The bridge consists of four box culverts with tide gates. MaineDOT invites the public to provide input on the purpose and need and range of alternatives to be considered, and to identify environmental impacts or issues related to the project.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before October 31, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Project information is available in the docket referenced above at 
                        <E T="03">www.regulations.gov</E>
                         and on the project website (
                        <E T="03">https://www.maine.gov/dot/major-projects/machias-dike-bridge-project</E>
                        ).
                    </P>
                    <P>Interested parties may submit comments by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Website:</E>
                         Go to the Federal eRulemaking Portal location at 
                        <E T="03">www.regulations.gov</E>
                         or the project website at 
                        <E T="03">https://www.maine.gov/dot/major-projects/machias-dike-bridge-project</E>
                        . Follow the online instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mailing address or for hand delivery or courier:</E>
                         MaineDOT Environmental Office, 24 Child Street, Augusta, ME 04330.
                    </P>
                    <P>
                        • 
                        <E T="03">Email address: environmentaloffice.mainedot@maine.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kristen Chamberlain, Senior Environmental Manager, MaineDOT Environmental Office, 24 Child Street Augusta, ME 04330; email: 
                        <E T="03">Kristen.chamberlain@maine.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The environmental review, consultation, and other actions required by applicable federal environmental laws for this project are being or have been carried out by MaineDOT pursuant to 23 U.S.C. 327 and a Memorandum of Understanding dated January 30, 2026, and executed by FHWA and MaineDOT.</P>
                <P>
                    MaineDOT, as the assigned National Environmental Policy Act (NEPA) lead agency, will prepare an EIS to evaluate transportation solutions for the Machias Dike Bridge on Route 1 in Machias, ME. The EIS will be conducted in accordance with the requirements of NEPA, as amended (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), 23 U.S.C. 139, FHWA regulations implementing NEPA (23 CFR part 771), and all applicable Federal, State, and local governmental laws and regulations. This project is considered a “major project” pursuant to 23 U.S.C. 139. MaineDOT will issue a single Final Environmental Impact Assessment and Record of Decision document pursuant to 23 U.S.C. 139(n)(2) unless MaineDOT determines statutory criteria or practicability considerations preclude issuance of a combined document.
                </P>
                <P>
                    <E T="03">(a) Request for Comment on Purpose and Need, Alternatives, Impacts, or Information:</E>
                     To ensure that a full range of issues related to the project are addressed and all potential issues are identified, MaineDOT invites comments and suggestions from all interested parties on the preliminary purpose and need, potential alternatives, or identification of any relevant information, studies, or analyses of any kind concerning impacts to the human environment to inform decision-making. Comments must be provided by October 31, 2026.
                </P>
                <P>
                    <E T="03">(b) Preliminary Purpose and Need for the Proposed Action:</E>
                     The preliminary purpose of this project is to achieve an overall bridge structure condition rating of Good (a rating of 7 or better on a scale of 0-9); and to preserve the Calais Branch Rail Corridor in the area in accordance with the State Railroad Preservation Act.
                </P>
                <P>The desired structural condition rating of at least a 7 indicates there are no noticeable or noteworthy deficiencies which affect the condition of the structure. This is in accordance with FHWA's Recording and Coding Guide for the Structure Inventory and Appraisal of the Nation's Bridges.</P>
                <P>
                    The need for the project is based on its structural condition. Bridge #2246 is over 92 years old and has a current structure rating of 4 on a scale of 0-9 based on routine inspections conducted in May and October 2023. The inspection indicated large spalls, heavy scaling, wide cracks, loss of rotten timber members, roadway settlements, and the need for numerous urgent and unscheduled repairs. Dive inspections were conducted in September and November 2023 and noted new areas of soil loss between the concrete slab 
                    <PRTPAGE P="42592"/>
                    under the road surface and the timber that forms the top of the gated boxes. In 2024, MaineDOT installed a temporary bridge over the existing structure to address immediate structural concerns. In April 2026, MaineDOT replaced the temporary bridge on top of the causeway with a longer-term interim structure. This action maintains traffic on Route 1 over the bridge and adjacent Sunrise Trail while thorough consideration of alternatives, the NEPA process, design and construction of a permanent solution that addresses the condition of the box culverts.
                </P>
                <P>
                    <E T="03">(c) A Preliminary Description of the Proposed Action Alternatives:</E>
                     The preliminary range of alternatives to be considered in the EIS includes the following: (1) taking no action; (2) fully gated replacement culverts; (3) partially gated replacement culverts; (4) replacement of the culverts with bridge span.
                </P>
                <P>
                    <E T="03">(d) Summary of Expected Impacts:</E>
                     The EIS will evaluate the expected social, economic, and environmental effects resulting from the action alternatives and the no action alternative. MaineDOT has identified the following preliminary issues for consideration: (1) Wetlands and Waters of the United States; (2) Historic Resources; (3) Section 4(f) Resources; (4) Endangered Species; (5) Essential Fish Habitat; (6) Property Impacts; (7) Downeast Sunrise Trail; (8) Community uses of Route 1 causeway; (9) municipal landfill; (10) transportation resiliency; (11) fish passage; and (12) tidal exchange.
                </P>
                <P>
                    <E T="03">(e) Anticipated Permits and Other Authorizations:</E>
                     The project will require a permit from the U.S. Army Corps of Engineers (USACE) under Section 404 of the Clean Water Act. Additional state permits that may be required include a Natural Resources Protection Act permit and Clean Water Act Section 401 Certification from the Maine Department of Environmental Protection (DEP), and Coastal Zone Consistency Determination from the Maine Coastal Program.
                </P>
                <P>
                    <E T="03">(f) Agency Coordination:</E>
                     Cooperating agencies have been preliminarily identified to include the USACE, the U.S. Environmental Protection Agency, National Marine Fisheries Service, U.S. Fish and Wildlife Service; and the U.S. Coast Guard. MaineDOT will prepare a coordination plan to define the agency and public participation procedures for the environmental review process. The plan will establish cooperating and participating agency roles and a review schedule.
                </P>
                <P>
                    <E T="03">(g) Agency and Public Review:</E>
                     All individuals and organizations expressing interest in the project will be able to participate in the process through various public outreach opportunities including public meetings and hearing(s). Public notice will be given regarding the time and place of all public meetings and hearing(s), and information will be posted on the project website and in newspapers with local and regional circulation.
                </P>
                <P>MaineDOT will initiate scoping with agencies, stakeholders and the public. MaineDOT will gather information and solicit input on the draft purpose and need statement for the project, the range of potential alternatives, and potentially significant environmental issues that will be evaluated in the EIS. The scoping process will include a public meeting and comment period.</P>
                <P>
                    Notice of availability of the Draft EIS for public and agency review will be published in the 
                    <E T="04">Federal Register</E>
                     and through other methods which will identify where interested parties can review a copy of the Draft EIS and how to provide comments. In addition, MaineDOT will conduct a public hearing for the Draft EIS. The public hearing will be announced a minimum of 15 days in advance.
                </P>
                <P>
                    <E T="03">(h) Preliminary Schedule for the Decision-Making Process:</E>
                     July 15-October 31, 2026: Agency and Public Scoping and comment period.
                </P>
                <P>
                    <E T="03">Spring 2027:</E>
                     Draft EIS issued for public and agency review and comment.
                </P>
                <P>
                    <E T="03">Fall 2027:</E>
                     Combined Final EIS and Record of Decision issued.
                </P>
                <EXTRACT>
                    <FP>
                        (Authority: 42 U.S.C. 4321 
                        <E T="03">et seq.;</E>
                         23 U.S.C. 139 and 327; 23 CFR part 771.)
                    </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Henry P. Rettinger IV,</NAME>
                    <TITLE>Maine Division Administrator, Federal Highway Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13876 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Transit Administration</SUBAGY>
                <SUBJECT>FY 2026 Competitive Funding Opportunity: Innovative Coordinated Access and Mobility</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Transit Administration (FTA), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of funding opportunity (NOFO).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Transit Administration (FTA) announces the opportunity to apply for approximately $12 million in competitive grants for the Fiscal Year (FY) 2026 Innovative Coordinated Access and Mobility (ICAM) Program.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Complete proposals must be submitted electronically through the 
                        <E T="03">GRANTS.GOV</E>
                         “APPLY” function by 11:59 p.m. Eastern time September 9, 2026.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Email Destiny Buchanan, Office of Program Management, at 
                        <E T="03">destiny.buchanan@dot.gov</E>
                         or (202) 366-2053.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The full text of the Notice of Funding Opportunity (NOFO) can be found on FTA's website at 
                    <E T="03">https://www.transit.dot.gov/funding/grants/notices</E>
                     and in the “FIND” module of 
                    <E T="03">GRANTS.GOV.</E>
                     The funding opportunity ID is FTA-2026-012-TPM-ICAM. Mail and fax submissions will not be accepted.
                </P>
                <SIG>
                    <NAME>Matthew Cahill,</NAME>
                    <TITLE>Acting Deputy Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13907 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Transportation Statistics Bureau</SUBAGY>
                <DEPDOC>[Docket No. DOT-OST-2026-1882]</DEPDOC>
                <SUBJECT>Notice of Request for Clearance of a Revision to a Currently Approved Information Collection: National Census of Ferry Operators</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Transportation Statistics (BTS), Office of the Assistant Secretary for Research and Technology (OST-R), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the requirements of the Paperwork Reduction Act of 1995, this notice announces the intention of the BTS to request the Office of Management and Budget's (OMB's) approval for new iterations of an on-going biennial information collection related to the nation's ferry operations. The information collected from each Census will be used to produce a descriptive database of existing ferry operations. A summary report of census findings will also be published by BTS on the BTS web page: 
                        <E T="03">www.bts.gov/ncfo.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before September 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments identified by DOT Docket ID Number DOT-OST-2026-1882 to the U.S. Department of Transportation (DOT), Docket Operations (DO). You may submit your comments by mail or in person to the Docket Clerk, Docket No. 
                        <PRTPAGE P="42593"/>
                        DOT-OST-2026-1882, U.S. Department of Transportation, Docket Operations, 1200 New Jersey Ave. SE, West Building 5th Floor W58-213, Washington, DC 20590. Comments should identify the docket number as indicated above. Paper comments should be submitted in duplicate. The DO is open for examination and copying, at the above address, from 9 a.m. to 5 p.m., Monday through Friday, except federal holidays. If you wish to receive confirmation of receipt of your written comments, please include a self-addressed, stamped postcard with the following statement: “Comments on Docket DOT-OST-2026-1882.” The Docket Clerk will date stamp the postcard prior to returning it to you via the U.S. mail. Please note that due to delays in the delivery of U.S. mail to Federal offices in Washington, DC, we recommend that persons consider an alternative method (the internet, fax, or professional delivery service) to submit comments to the docket and ensure their timely receipt at U.S. DOT. You may fax your comments to the DO at (202) 493-2251. Comments can also be viewed and/or submitted via the Federal Rulemaking Portal: 
                        <E T="03">http://www.regulations.gov.</E>
                    </P>
                    <P>
                        Please note that anyone is able to electronically search all comments received into our docket management system by the name of the individual submitting the comment (or signing the comment if submitted on behalf of an association, business, labor union, etc.). You may review DOT's complete Privacy Act Statement in the 
                        <E T="04">Federal Register</E>
                         published on April 11, 2000 (Volume 65, Number 70; pages 19475-19570) or you may review the Privacy Act Statement at 
                        <E T="03">http://www.gpoaccess.gov/fr/.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Kenneth Steve, (202) 579-0672, NCFO Program Manager, BTS, OST-R, Department of Transportation, 1200 New Jersey Ave. SE, Room E36-308, Washington, DC 20590. Office hours are from 8:00 a.m. to 5:30 p.m., E.T., Monday through Friday, except Federal holidays.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title:</E>
                     National Census of Ferry Operators (NCFO)
                </P>
                <P>
                    <E T="03">Background:</E>
                     The Transportation Equity Act for the 21st Century (TEA-21) (Pub. L. 105-178), section 1207(c), directed the Secretary of Transportation to conduct a study of ferry transportation in the United States and its possessions. In 2000, the Federal Highway Administration (FHWA) Office of Intermodal and Statewide Planning conducted a survey of approximately 260 ferry operators to identify: (1) existing ferry operations including the location and routes served; (2) source and amount, if any, of funds derived from Federal, State, or local governments supporting ferry construction or operations; (3) potential domestic ferry routes in the United States and its possessions and to develop information on those routes; and (4) potential for use of high speed ferry services and alternative-fueled ferry services. The Safe, Accountable, Flexible Efficient Transportation Equity Act—A Legacy for Users (SAFETEA-LU) Public Law 109-59, Section 1801(e)) required that the Secretary, acting through the BTS, shall establish and maintain a national ferry database containing current information regarding routes, vessels, passengers and vehicles carried, funding sources and such other information as the Secretary considers useful. MAP-21 legislation [Moving Ahead for Progress in the 21st Century Act (Pub. L. 112-141),] continued the BTS mandate to conduct the NCFO and also required that the Federal Highway Administration (FHWA) use the NCFO data to set the specific formula for allocating federal ferry funds. The funding allocations were based on a percentage of the number of passenger boardings, vehicle boardings, and route miles served.
                </P>
                <P>The FAST Act legislation [Fixing America's Surface Transportation Act (Pub. L. 114-94, sec. 1112)] continues the BTS mandate to conduct the NCFO on a biennial basis, and extended the requirement that the Federal Highway Administration (FHWA) use the NCFO data to set the specific formula for allocating federal ferry funds based on a percentage of the number of passenger boardings, vehicle boardings, and route miles served. For the 2026 NCFO, the length of the revised questionnaire for the 2026 NCFO will remain consistent with that of previous years. Research will be conducted during 2027 to early 2028, between the 2026 and 2028 NCFOs, using cognitive interviews with ferry operators with the goal of updating the questionnaire to reduce respondent burden and promote higher response rates.</P>
                <P>BTS conducted the first Census of Ferry Operators in 2006, and again in 2008, 2010, 2014, 2016, 2018, 2020, 2022, and 2024 and plans are underway for the conduct of the next NCFO in the Spring of 2027. During the 2022 Census, the operation schedule was changed so that data would be collected in in the year following the NCFO, for example, data was collected in 2025 for ferry operations in the 2024 NCFO. These information collections were originally approved by OMB under Control Number 2139-0009.</P>
                <P>The census will be administered to the entire population of ferry operators (estimate of 260 or less). The census will request the respondents to provide information such as: the terminals served; the type of ownership; the number of passengers and vehicles carried in the past 12 months; vessel descriptions (including type of fuel), federal, state and local funding sources, and intermodal connectivity. All data collected in the 2026 and 2028 NCFOs will be added to the existing NCFO database.</P>
                <P>
                    <E T="03">Respondents:</E>
                     The target population for the census will be all of the approximately 260 ferry operators existing in the United States.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Response:</E>
                     The burden per respondent is estimated to be an average of 30 minutes. This average is based on an estimate of 20 minutes to answer new questions and an additional 10 minutes to review (and revise as needed) previously submitted data that will be pre-populated for each ferry operation.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     The total annual burden for the 2026 NCFO is estimated to be 130 hours (that is 30 minutes per respondent for 260 respondents equals 7,800 minutes). For the research performed between the census cycles, no more than 9 operators will be interviewed for about 60 minutes. This research will help to reduce the burden for respondents. The total annual burden for the 2028 NCFO is estimated to be 108.33 hours (that is 25 minutes per respondent for 260 respondents equals 6,500 minutes).
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     This census will be updated every other year.
                </P>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     Interested parties are invited to send comments regarding any aspect of this information collection, including, but not limited to: (1) the necessity and utility of the information collection for the proper performance of the functions of the DOT; (2) the accuracy of the estimated burden; (3) ways to enhance the quality, utility, clarity and content of the collected information; and (4) ways to minimize the collection burden without reducing the quality of the collected information. Comments submitted in response to this notice will be summarized and/or included in the request for OMB's clearance of this information collection.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     The Transportation Equity Act for the 21st Century, Public Law 105-178, section 1207(c), The Safe, Accountable, Flexible Efficient Transportation Equity Act—A Legacy for Users (SAFETEA-LU), Public Law 
                    <PRTPAGE P="42594"/>
                    109-59, Moving Ahead for Progress in the 21st Century Act (MAP-21), Public Law 112-141, 49 CFR 1.46, and Fixing America's Surface Transportation Act (FAST Act), Public Law 114-94, sec. 1112.
                </P>
                <SIG>
                    <P>Issued in Washington, DC.</P>
                    <NAME>Cha-Chi Fan,</NAME>
                    <TITLE>Director, Office of Data Development and Standards, Bureau of Transportation Statistics, Office of the Assistant Secretary for Research and Technology.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13855 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-9X-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Bureau of the Fiscal Service</SUBAGY>
                <SUBJECT>Prompt Payment Interest Rate; Contract Disputes Act</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of the Fiscal Service, Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of prompt payment interest rate; Contract Disputes Act.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>For the period beginning July 1, 2026, and ending on December 31, 2026, the prompt payment interest rate is 4-3/4 per centum per annum.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable July 1, 2026, to December 31, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments or inquiries may be mailed to: Alternative Payments Division, Bureau of the Fiscal Service, 801 9th Street NW, Washington, DC 20220. Comments or inquiries may also be emailed to 
                        <E T="03">PromptPayment@fiscal.treasury.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Pavita Murthi, Alternative Payments Division, (202) 874-5303; or Ashlee Adams, Senior Counsel, Office of the Chief Counsel, (304) 480-8692.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>An agency that has acquired property or service from a business concern and has failed to pay for the complete delivery of property or service by the required payment date shall pay the business concern an interest penalty. 31 U.S.C. 3902(a). The Contract Disputes Act of 1978, sec. 12, Public Law 95-563, 92 Stat. 2389, and the Prompt Payment Act, 31 U.S.C. 3902(a), provide for the calculation of interest due on claims at the rate established by the Secretary of the Treasury.</P>
                <P>The Secretary of the Treasury has the authority to specify the rate by which the interest shall be computed for interest payments under section 12 of the Contract Disputes Act of 1978 and under the Prompt Payment Act. Under the Prompt Payment Act, if an interest penalty is owed to a business concern, the penalty shall be paid regardless of whether the business concern requested payment of such penalty. 31 U.S.C. 3902(c)(1). Agencies must pay the interest penalty calculated with the interest rate, which is in effect at the time the agency accrues the obligation to pay a late payment interest penalty. 31 U.S.C. 3902(a). “The interest penalty shall be paid for the period beginning on the day after the required payment date and ending on the date on which payment is made.” 31 U.S.C. 3902(b).</P>
                <P>
                    Therefore, notice is given that the Secretary of the Treasury has determined that the rate of interest applicable for the period beginning July 1, 2026, and ending on December 31, 2026, is 4
                    <FR>3/4</FR>
                     per centum per annum.
                </P>
                <SIG>
                    <NAME>Joseph Gioeli, III,</NAME>
                    <TITLE>Acting Commissioner, Bureau of the Fiscal Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13903 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Internal Revenue Service</SUBAGY>
                <SUBJECT>Agency Information Collection Activities; Comment Request on Notice of Qualified Equity Investment for New Markets Credit</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of information collection; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, the IRS is inviting comments on the information collection request outlined in this notice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before September 8, 2026 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 Control No. 1545-2065” 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 Marcus W. McCrary, 470-769-2001.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The IRS, in accordance with the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3506(c)(2)(A)), provides the general public and Federal agencies with an opportunity to comment on proposed, revised, and continuing collections of information. This helps the IRS assess the impact and minimize the burden of its information collection requirements. 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, and viewable on relevant websites. For this reason, please do not include in your comments information of a confidential nature, such as sensitive personal information. </P>
                <P>
                    <E T="03">Comments are invited on:</E>
                     (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>
                <P>
                    <E T="03">Title:</E>
                     Notice of Qualified Equity Investment for New Markets Credit.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1545-2065.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     8874-A.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Community Development Entities (CDEs) must provide notice to any taxpayer who acquires a qualified equity investment in the CDE at its original issue that the equity investment is a qualified equity investment entitling the taxpayer to claim the new markets credit. Form 8874-A is used to make the notification as required under Regulations section 1.45D-1(g)(2)(i)(A).
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     There is no change to the previously approved information collection. However, the burden was recalculated for a better estimate.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Business, other for-profit organizations, and Not-for-profit organizations.
                </P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     500.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     5 hours, 24 minutes.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     2,700.
                </P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Marcus W. McCrary,</NAME>
                    <TITLE>Tax Analyst.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13909 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4831-GV-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="42595"/>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBJECT>Government Securities: Call for Large Position Reports</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of call for Large Position Reports.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Department of the Treasury (Treasury) called for the submission of Large Position Reports by entities whose positions in the Treasury Floating Rate Note due January 2026 equaled or exceeded $8.4 billion as of Friday, January 23, 2026 or Friday, January 30, 2026.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Reports must be received by 12:00 p.m. Eastern Time on Monday, July 13, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        All entities are encouraged to submit reports using Treasury's webform (available at 
                        <E T="03">https://www.treasurydirect.gov/laws-and-regulations/gsa/lpr-form/</E>
                        ). Reports may also be faxed to Treasury at (202) 504-3788 if a reporting entity has difficulty using the webform.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Lori Santamorena, Kevin Hawkins, John Garrison, or Luisa Jou-Penchev, Office of Securities Regulatory Operations, Office of Financing, at 202-504-3632 or 
                        <E T="03">govsecreg@fiscal.treasury.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In a public announcement issued on July 7, 2026, Treasury called for Large Position Reports from entities whose positions in the Treasury Floating Rate Note due January 2026 (CUSIP 91282CJU6) equaled or exceeded $8.4 billion as of Friday, January 23, 2026 or Friday, January 30, 2026. Entities with positions in this Treasury Floating Rate Note below the reporting threshold as of the reporting date are not required to submit Large Position Reports.</P>
                <P>This call for Large Position Reports is pursuant to Treasury's large position reporting rules (17 CFR part 420) under the Government Securities Act, as amended (see 15 U.S.C. 78o-5(f)). Reports must be received by Treasury before 12:00 p.m. Eastern Time on Monday, July 13, 2026, and must include the required positions and administrative information.</P>
                <P>The Treasury Floating Rate Note due January 2026 has a CUSIP number of 91282CJU6 and a maturity date of January 31, 2026.</P>
                <P>
                    The public announcement, a sample Large Position Report (which appears in Appendix B of the large position reporting rules at 17 CFR part 420), supplementary formula guidance, and a series of training modules are available at 
                    <E T="03">https://www.treasurydirect.gov/laws-and-regulations/gsa/lpr-reports/.</E>
                </P>
                <P>The collection of large position information has been approved by the Office of Management and Budget pursuant to the Paperwork Reduction Act under OMB Control Number 1530-0064.</P>
                <SIG>
                    <NAME>Brian Smith,</NAME>
                    <TITLE>Deputy Assistant Secretary for Federal Finance.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13862 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-AK-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <DEPDOC>[Docket No. VA-2025-VACO-0001]</DEPDOC>
                <SUBJECT>Privacy Act of 1974; System of Records</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Veterans Benefits Administration (VBA), Department of Veterans Affairs (VA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a modified system of records.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the Privacy Act of 1974, notice is hereby given that VA is modifying a system of records in its inventory titled, Beneficiary Fiduciary Field System (BFFS)-VA (37VA27). This system contains records used for the administration of benefits regarding beneficiaries who VA or a court has deemed unable to manage their financial affairs.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Comments on this modified system of records must be received no later than 30 days after the date of publication in the 
                        <E T="04">Federal Register</E>
                        . If no public comment is received during the period allowed for comment or unless otherwise published in the 
                        <E T="04">Federal Register</E>
                         by VA, the modified system of records will become effective a minimum of 30 days after date of publication in the 
                        <E T="04">Federal Register</E>
                        . If VA receives public comments, VA shall review the comments to determine whether any changes to the notice are necessary.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted through 
                        <E T="03">www.regulations.gov</E>
                         under docket number VA-2025-VACO-0001 or mailed to VA Privacy Service (005X6F), 810 Vermont Avenue NW, Washington, DC 20420. Comments must indicate that they are submitted in response to Supervised Fiduciary/Beneficiary and General Investigative Records—VA (37VA27). Comments received will be available at 
                        <E T="03">www.regulations.gov</E>
                         for public viewing, inspection, or copies.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Seamus Welch, Analyst, Pension and Fiduciary Service, VA, 810 Vermont Avenue NW, Washington, DC 20420, 
                        <E T="03">Seamus.Welch@va.gov,</E>
                         or by telephone at 202-461-9759. (This is not a toll-free number.)
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>VA is modifying this system of records by revising the system name; routine uses; policies and practices for storage of records; policies and practices for retrieval of records; policies and practices for retention and disposal of records; record access procedures; contesting records procedures; and notification procedures. VA is republishing the system notice in its entirety.</P>
                <P>VA is modifying:</P>
                <P>• The name of the system of records from BFFS-VA (37VA27) to Supervised Fiduciary/Beneficiary and General Investigative Records—VA (37VA27).</P>
                <P>• Routine use numbers 1-23 to reflect new language.</P>
                <P>• The Policies and Practices for Storage of Records section to state, “VA maintains records at the VA fiduciary hub that has jurisdiction over the geographical area in which the VA beneficiary resides, and the Corporate Franchise Data Center in Austin, Texas. Non-fiduciary program investigations and related information are maintained stored at the fiduciary hubs and at VA Central Office SharePoint websites.”</P>
                <P>• The Policies and Practices for Retrieval of Records section to state, “Records in this system are retrieved by the name of the individual and VA file number.”</P>
                <P>• The Policies and Practices for Retention and Disposal of Records section is being modified to state, “Records in this system are retained and disposed of in accordance with the schedule approved by the Archivist of the United States, VBA Records Control Schedule VB-1, Part 1, Section VI, Item Numbers: 06-016.000 through 06-025.000.”</P>
                <P>• The Record Access Procedures section to state, “Individuals seeking information on the existence and content of records in this system pertaining to them should contact the system manager in writing as indicated above or may write or visit the VA facility location where they normally receive their care. A request for access to records must contain the requester's full name, address, telephone number, be signed by the requester, and describe the records sought in sufficient detail to enable VA personnel to locate them with a reasonable amount of effort.”</P>
                <P>
                    • The Contesting Records Procedures section to state, “Individuals seeking to contest or amend records in this system pertaining to them should contact the 
                    <PRTPAGE P="42596"/>
                    system manager in writing as indicated above or may write or visit the VA facility location where they normally receive their care. A request to contest or amend records must state clearly and concisely what record is being contested, the reasons for contesting it, and the proposed amendment to the record.”
                </P>
                <P>• The Notification Procedures section to state, “Generalized notice is provided by the publication of this notice. For specific notice, see Record Access Procedure, above.”</P>
                <P>VA is proposing to update this system of records notice to include authority to disclose the necessary fiduciary information to surety bond companies when there has been a misuse determination. Pursuant to 38 CFR 14.709(a), “It is the policy of the Department of Veterans Affairs to require, where possible under State laws and rules of the court, corporate surety bonds in all court-appointed fiduciary cases where the fiduciary is an individual and the estate is sufficient to justify the expense of procuring a corporate surety bond. Corporate bonds may be required of corporate fiduciaries in accordance with State laws.” In addition, 38 CFR 13.230(a) requires a VA-appointed fiduciary to “furnish to the fiduciary hub with jurisdiction a corporate surety bond that is conditioned upon faithful discharge of all of the responsibilities of a fiduciary prescribed in § 13.140 and meets the requirements of [§ 13.230(d)], if the VA benefit funds that are due and to be paid for the beneficiary will exceed $25,000 at the time of appointment.” A corporate surety bond is not required when a VA-appointed fiduciary is (i) a trust company or a bank with trust powers organized under the laws of the United States or a state; (ii) the beneficiary's spouse; (iii) located in Puerto Rico, Guam, or the Philippines and has entered into a restricted withdrawal agreement in lieu of a surety bond; (iv) a fiduciary that is also appointed by a court and has obtained a state-court bond that is sufficient to cover VA and non-VA funds; or (v) a fiduciary that is also a state agency with existing state-mandated liability insurance or a blanket bond sufficient to cover VA and non-VA funds.</P>
                <P>VA requires surety bonds for court-appointed fiduciaries to be in an amount commensurate with the value of the personal estate derived from VA benefits plus the anticipated net income from VA benefits received during the ensuing accounting period. See 38 CFR 14.709(c). VA requires surety bonds for VA-appointed fiduciaries to be “in an amount sufficient to cover the value of the VA benefit funds under management by the fiduciary for the beneficiary” and requires fiduciaries, after furnishing the prescribed bond to the fiduciary hub, to “adjust the bond amount to account for any increase or decrease of more than 20 percent in the VA benefit funds under management by the fiduciary for the beneficiary.” 38 CFR 13.230.</P>
                <P>The new Routine Use 24 will authorize VBA fiduciary hubs to provide the surety bond companies with the following documentation: (1) unredacted copies of the misuse determination, (2) all documentation the principal provided to VA relative to the time period for which the principal acted as fiduciary of the beneficiary, (3) all accounting and banking records for the veteran for the relevant time period, (4) the identity and contact information of the beneficiary's successor fiduciary, (5) any investigative reports or records completed by VA., and (6) any additional information in VA's possession related to its claim on the surety bond.</P>
                <P>The Report of Intent to Amend a System of Record Notice and an advance copy of the system notice was sent to the appropriate Congressional Committees and to the Office of Management and Budget (OMB) as required by 5 U.S.C. 552a(r) (Privacy Act) and guidelines issued by OMB (81 FR 94424), December 23, 2016.</P>
                <HD SOURCE="HD1">Signing Authority</HD>
                <P>The Senior Agency Official for Privacy, or designee, approved this document and authorized the undersigned to sign and submit the document to the Office of the Federal Register for publication electronically as an official document of the Department of Veterans Affairs. Eddie Pool, Deputy Chief Information Officer, Performing the Delegable Duties of the Assistant Secretary for Information and Technology and Chief Information Officer, Department of Veterans Affairs approved this document on September 12, 2025 for publication.</P>
                <SIG>
                    <DATED>Dated: July 7, 2026.</DATED>
                    <NAME>Saurav Devkota,</NAME>
                    <TITLE>Government Information Specialist, VA Privacy Service, Office of Information and Technology, Department of Veterans Affairs.</TITLE>
                </SIG>
                <PRIACT>
                    <HD SOURCE="HD2">SYSTEM NAME AND NUMBER:</HD>
                    <P>Supervised Fiduciary/Beneficiary and General Investigative Records—VA (37VA27).</P>
                    <HD SOURCE="HD2">SECURITY CLASSIFICATION:</HD>
                    <P>Unclassified.</P>
                    <HD SOURCE="HD2">SYSTEM LOCATION:</HD>
                    <P>Records are maintained at the VA fiduciary hub that has jurisdiction over the geographical area in which the VA beneficiary resides, and the Corporate Franchise Data Center in Austin, Texas. The supervised fiduciary/beneficiary and general investigative records and associated electronic records are maintained at a private Federal hosting facility. The addresses of VA fiduciary hubs and the data processing center are listed in VA Appendix 1.</P>
                    <HD SOURCE="HD2">SYSTEM MANAGER(S):</HD>
                    <P>
                        Mr. Seamus Welch, Analyst, Pension and Fiduciary Service, Veterans Benefits Administration Department of Veterans Affairs, 810 Vermont Avenue NW, Washington, DC 20420. Mr. Welch may be reached at 
                        <E T="03">Seamus.Welch@va.gov,</E>
                         or 202-461-9759. (This is not a toll-free number.)
                    </P>
                    <HD SOURCE="HD2">AUTHORITY FOR MAINTENANCE OF THE SYSTEM:</HD>
                    <P>38 U.S.C. 55, 501(a)-(b).</P>
                    <HD SOURCE="HD2">PURPOSE(S) OF THE SYSTEM:</HD>
                    <P>VA's fiduciary system protects vulnerable VA beneficiaries who cannot manage their benefits due to injury, disease, or age. VA qualifies individuals for service as a fiduciary and provides oversight of fiduciaries. VA collects and maintains records to enable it to administer these benefit programs.</P>
                    <HD SOURCE="HD2">CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:</HD>
                    <P>The following categories of individuals are covered by this system:</P>
                    <P>1. VA beneficiaries (such as a veteran or a non-veteran adult who receives VA monetary benefits, lacks the mental capacity to manage their own financial affairs regarding disbursement of funds without limitation, and is either rated incapable of managing their financial affairs or adjudged to be under legal disability by a court of competent jurisdiction; or a child who has not reached majority under state law and receives VA monetary benefits).</P>
                    <P>2. Current, former, and prospective VA-appointed fiduciaries (such as a VA Federal fiduciary appointed by VA to serve as fiduciary of VA monetary benefits for a VA beneficiary determined unable to manage their financial affairs; or a person or legal entity appointed by a state or foreign court to supervise the person and/or payee of a VA beneficiary adjudged to be under a legal disability). The statutory title of a court appointed fiduciary may vary from state to state.</P>
                    <P>
                        3. A chief officer of a hospital, domiciliary, institution, or nursing home care facility where a beneficiary, who VA has determined is unable to 
                        <PRTPAGE P="42597"/>
                        manage their financial affairs, is receiving care and who has contracted to use the veteran's VA funds in a specific manner.
                    </P>
                    <P>4. Supervised Direct Payment (such as an adult beneficiary in the fiduciary program who manages their VA benefits with limited and temporary supervision based upon a field examination and subsequent to determination by the hub manager pertaining to benefits eligibility and other issues; or, to develop evidence for further investigations of potential criminal issues).</P>
                    <P>5. Physicians named in treatment records and financial managers or attorneys who help disperse funds for VA beneficiaries deemed unable to manage those funds.</P>
                    <HD SOURCE="HD2">CATEGORIES OF RECORDS IN THE SYSTEM:</HD>
                    <P>The records in the electronic fiduciary folder are the primary records in this system. These records may contain the following types of information:</P>
                    <P>1. Field examination reports (such as the VA Form 27-4716a or 27-3190, Field Examination Request and Report, which contains a VA beneficiary's name, address, Social Security number (SSN), VA file number, an assessment of the beneficiary's ability to handle VA and non-VA funds, description of family relationships, economic and social adjustment information, information on the beneficiary's activities, and the name, address, and assessment of the performance of a VA-appointed fiduciary).</P>
                    <P>2. Correspondence from and to a VA beneficiary, a VA appointed fiduciary, and other interested third parties.</P>
                    <P>3. Medical records (such as medical and social work reports generated in VA, state, local, or private medical treatment facilities or private physicians' offices indicating the medical history of a VA beneficiary, including diagnosis, treatment and nature of any physical or mental disability).</P>
                    <P>4. Financial records (such as accountings regarding a fiduciary's management of a beneficiary's income, investments, and accumulated funds, monthly benefit amount received, amounts charged for fees by the fiduciary, certificates of balance on accounts from financial institutions, and withdrawal agreements between VA, financial institutions, and the fiduciary).</P>
                    <P>5. Court documents (such as petitions, court orders, letters of guardianship, Inventories of assets, and depositions).</P>
                    <P>6. Agreements to serve as a VA Federal fiduciary.</P>
                    <P>7. Information pertaining to individuals, including companies and other entities, who previously served as a VA appointed fiduciary.</P>
                    <P>8. Information related to the qualification and appointment of individuals, including companies and other entities, considered by VA for appointment as a fiduciary.</P>
                    <P>9. Photographs of people (beneficiaries who VA has determined are unable to manage their financial affairs, fiduciaries, and other persons who are the subject of a VA investigation), places, and things that are related to the subject of a VA investigation as part of VA's oversight duties.</P>
                    <P>10. Fingerprint records.</P>
                    <P>11. SSA records containing information about the type and amount of SSA benefits paid to beneficiaries who are eligible to receive benefits under VA and SSA eligibility criteria, records containing information developed by SSA about SSA beneficiaries who need representative payees, accountings provided to SSA, and records containing information about SSA representative payees. These records are reports of field examinations or investigations performed at the request of any organizational element of VA about any subject under the jurisdiction of VA other than a fiduciary issue. In addition to copies of the reports, records may include copies of exhibits or attachments such as photographs of people, places, and things; sworn statements; legal documents involving loan guaranty transactions, bankruptcy, and debts owed to VA; accident reports; birth, death, and divorce records; certification of search for vital statistics documents; beneficiary's financial statements and tax records; immigration information; and newspaper clippings.</P>
                    <HD SOURCE="HD2">RECORD SOURCE CATEGORIES:</HD>
                    <P>VA beneficiary, VA beneficiary's dependents, VA-appointed fiduciaries, individuals who were previously VA-appointed fiduciaries; individuals who VA considered for service as a VA appointed fiduciary but were not selected; field examiners; legal instrument examiners; fiduciary program personnel; third parties (medical care and service providers, friends, relatives); other Federal, state, and local agencies (public assistance offices, courts, benefit providers); and VA records.</P>
                    <HD SOURCE="HD2">ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:</HD>
                    <P>
                        1. 
                        <E T="03">Congress:</E>
                         To a Member of Congress or staff acting upon the Member's behalf when the Member or staff requests the information on behalf of, and at the request of, the individual who is the subject of the record.
                    </P>
                    <P>
                        2. 
                        <E T="03">Data Breach Response and Remediation for VA:</E>
                         To appropriate agencies, entities, and persons when (a) VA suspects or has confirmed that there has been a breach of the system of records, (b) VA has determined that as a result of the suspected or confirmed breach there is a risk of harm to individuals, VA (including its information systems, programs, and operations), the Federal Government, or national security, and (c) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with VA's efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm.
                    </P>
                    <P>
                        3. 
                        <E T="03">Data Breach Response and Remediation for Another Federal Agency:</E>
                         To another Federal agency or Federal entity, when VA determines that the information from this system of records is reasonably necessary to assist the recipient agency or entity in (a) responding to a suspected or confirmed breach or (b) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach.
                    </P>
                    <P>
                        4. 
                        <E T="03">Law Enforcement:</E>
                         To a Federal, state, local, territorial, tribal, or foreign law enforcement authority or other appropriate entity charged with the responsibility of investigating or prosecuting a violation or potential violation of law, whether civil, criminal, or regulatory in nature, or charged with enforcing or implementing such law, provided that the disclosure is limited to information that, either alone or in conjunction with other information, indicates such a violation or potential violation. The disclosure of the names and addresses of veterans and their dependents from VA records under this routine use also must comply with the provisions of 38 U.S.C. 5701.
                    </P>
                    <P>
                        5. 
                        <E T="03">Department of Justice (DOJ), Litigation, Administrative Proceeding:</E>
                         To DOJ, or in a proceeding before a court, adjudicative body, or other administrative body before which VA is authorized to appear, when (a) VA or any component thereof, (b) Any VA employee in their official capacity, (c) any VA employee in their individual capacity where DOJ has agreed to represent the employee, or (d) the United States, where VA determines that litigation is likely to affect the agency or any of its components, is a 
                        <PRTPAGE P="42598"/>
                        party to such proceedings or has an interest in such proceedings, and VA determines that use of such records is relevant and necessary to the proceedings.
                    </P>
                    <P>
                        6. 
                        <E T="03">Contractors:</E>
                         To contractors, grantees, experts, consultants, students, and others performing or working on a contract, service, grant, cooperative agreement, or other assignment for VA, when reasonably necessary to accomplish an agency function related to the records.
                    </P>
                    <P>
                        7. 
                        <E T="03">National Archives and Records Administration (NARA):</E>
                         To NARA in records management inspections conducted under 44 U.S.C. 2904 and § 2906, or other functions authorized by laws and policies governing NARA operations and VA records management responsibilities.
                    </P>
                    <P>
                        8. 
                        <E T="03">Governmental Agencies, Health Organizations for Claimants' Benefits:</E>
                         To Federal, state, and local government agencies as reasonably necessary to assist in the development of programs that will be beneficial to claimants, to further protect their rights under law, and ensure that they are receiving all benefits to which they are entitled.
                    </P>
                    <P>
                        9. 
                        <E T="03">SSA for Fiduciaries:</E>
                         To a representative of the SSA to the extent necessary for the operation of a VA program, name, address, SSN, VA file number, medical records, financial records, and field examination reports of a VA beneficiary who is in receipt of VA and SSA benefits concurrently, and the name, address, and information regarding the activities of a VA supervised fiduciary serving in that role.
                    </P>
                    <P>
                        10. 
                        <E T="03">Federal and State Agencies for Benefits:</E>
                         To a Federal agency, upon its official request, the name and address of a VA beneficiary, the VA rating that indicates the beneficiary is unable to manage their financial affairs, and the field examination report upon which the rating was based may be disclosed in order for that agency to make decisions on such matters as competency and dependency in connection with eligibility for that agency's benefits. This information also may be disclosed to a state or local agency, upon its official request, in order for that agency to make decisions on such matters as competency and dependency in connection with eligibility for that agency's benefits, if the information pertains to a VA beneficiary who is not a veteran, or if the name and address of the veteran is provided beforehand.
                    </P>
                    <P>
                        11. 
                        <E T="03">Guardians, Courts for Guardianship:</E>
                         To a court, magistrate, or administrative tribunal in matters of guardianship, inquests, and commitments, and to probation and parole officers in connection with court required duties; medical records, financial records, field examination reports, correspondence, and court documents may be disclosed in the course of presenting evidence.
                    </P>
                    <P>
                        12. 
                        <E T="03">Third Parties for VA Investigations:</E>
                         To a third party who may have information regarding a VA investigation, including information in VA records obtained from the SSA, and the name and address of a VA beneficiary, fiduciary, or other person under investigation.
                    </P>
                    <P>
                        13. 
                        <E T="03">Proposed Fiduciary:</E>
                         To a proposed fiduciary, VA beneficiary information contained in this system in order for the fiduciary to make an informed decision with regard to accepting fiduciary responsibility for a VA beneficiary.
                    </P>
                    <P>
                        14. 
                        <E T="03">Guardian Ad Litem for Representation:</E>
                         To a fiduciary or guardian ad litem in relation to his or her representation of a claimant in any legal proceeding as relevant and necessary to fulfil the duties of the fiduciary or guardian ad litem.
                    </P>
                    <P>
                        15. 
                        <E T="03">Federal, State Agencies for Debts Owed:</E>
                         To other Federal agencies, state probate courts, state driver's license bureaus, state automobile title and license bureaus, any available identifying information regarding the debtor, such as the name of the debtor, last known address of the debtor, name of debtor's spouse, SSN, VA insurance number, VA file number, place of birth and date of birth of debtor, name and address of debtor's employer or firm, and dates of employment may be disclosed to obtain current address, locator, and credit report assistance in the collection of unpaid financial obligations owed the United States in accordance with the Federal Claims Collection Act of 1966 and 38 U.S.C. 5701(b)(6).
                    </P>
                    <P>
                        16. 
                        <E T="03">Lenders for Loan Guarantee:</E>
                         To a lender or prospective lender participating in the VA Loan Guaranty Program who is extending credit or proposing to extend credit on behalf of a veteran, any information in this system relating to the adjudication of a VA beneficiary's ability to manage their VA benefits, either by a court of competent jurisdiction or by VA, may be disclosed.
                    </P>
                    <P>
                        17. 
                        <E T="03">VA Beneficiary for VA Fiduciary Appointment:</E>
                         To the beneficiary or their accredited representative or court appointed guardian for the purpose of notifying the beneficiary of the reasons for selection or non-selection of the individual.
                    </P>
                    <P>
                        18. 
                        <E T="03">VA Beneficiary for Fiduciary Misuse Notification:</E>
                         To the beneficiary or their accredited representative or court appointed guardian for the purpose of notifying the beneficiary of the reasons for VA's decision regarding misuse.
                    </P>
                    <P>
                        19. 
                        <E T="03">Surety Bond Companies:</E>
                         To attorneys, insurance companies, third parties liable or potentially liable under surety bond contracts, and courts, boards, or commissions, to the extent necessary to aid VA in the preparation, presentation, and prosecution of claims authorized under Federal, state, or local laws, and regulations promulgated thereunder.
                    </P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR STORAGE OF RECORDS:</HD>
                    <P>VA maintains records at the VA fiduciary hub that has jurisdiction over the geographical area in which VA beneficiary resides, and the Corporate Franchise Data Center in Austin, Texas. Non-fiduciary program investigations and related information are maintained at the fiduciary hubs and at VA Central Office SharePoint websites.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:</HD>
                    <P>Records in this system are retrieved by the name of the individual and the VA file number.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:</HD>
                    <P>Records in this system are retained and disposed of in accordance with the schedule approved by the archivist of the United States, VBA Records Control Schedule VB-1, Part 1, Section VI, Item Numbers: 06-016.000 through 06-025.000.</P>
                    <HD SOURCE="HD2">ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:</HD>
                    <P>1. Physical Security:</P>
                    <P>a. Access to working spaces and claims folder file storage areas in VA regional offices and centers is restricted to VA employees on a need-to-know basis. Generally, file areas are locked after normal duty hours, and the offices and centers are protected from outside access by the Federal Protective Service or other security personnel. Employee claims file records and claims file records of public figures are stored in separate locked files. Strict control measures are enforced to ensure that access to and disclosure from these claims file records are limited to a need-to-know basis. Duplicate paper copies after imaging are stored in NARA-compliant facilities, pending destruction.</P>
                    <P>
                        b. Veterans Benefits Management System access is protected by the usage of “login” identification passwords and authorized function passwords. The passwords are changed periodically. 
                        <PRTPAGE P="42599"/>
                        These same protections apply to remote access users.
                    </P>
                    <HD SOURCE="HD2">RECORD ACCESS PROCEDURES:</HD>
                    <P>Individuals seeking information on the existence and content of records in this system pertaining to them may contact the system manager in writing as indicated herein or may write or visit the VA facility location where they normally receive their care. A request for access to records must contain the requester's full name, address, telephone number, be signed by the requester, and describe the records sought in sufficient detail to enable VA personnel to locate them with a reasonable amount of effort.</P>
                    <HD SOURCE="HD2">CONTESTING RECORD PROCEDURES:</HD>
                    <P>Individuals seeking to contest or amend records in this system pertaining to them should contact the system manager in writing as indicated herein or may write or visit the VA facility location where they normally receive their care. A request to contest or amend records must state clearly and concisely what record is being contested, the reasons for contesting it, and the proposed amendment to the record.</P>
                    <HD SOURCE="HD2">NOTIFICATION PROCEDURES:</HD>
                    <P>Generalized notice is provided by the publication of this notice. For specific notice, see the Record Access Procedure section herein.</P>
                    <HD SOURCE="HD2">EXEMPTIONS PROMULGATED FOR THE SYSTEM:</HD>
                    <P>None.</P>
                    <HD SOURCE="HD2">HISTORY:</HD>
                    <P>79 FR 41744 (July 17, 2014).</P>
                </PRIACT>
                <HD SOURCE="HD1">Appendix 1: VA Regional Offices With Fiduciary Activity</HD>
                <EXTRACT>
                    <P>Please send address and telephone number corrections to Department of Veterans Affairs, Pension and Fiduciary Service (21PF), 810 Vermont Avenue NW, Washington, DC 20420.</P>
                    <HD SOURCE="HD2">• Columbia Fiduciary Hub</HD>
                    <FP SOURCE="FP-1">○ Jurisdiction for Florida, Georgia, North Carolina, South Carolina; Office/Mail: 6437 Garners Ferry Road, Columbia, SC 29209; Phone: 1-888-407-0144; press # 1</FP>
                    <HD SOURCE="HD2">• Indianapolis Fiduciary Hub</HD>
                    <FP SOURCE="FP-1">○ Jurisdiction for Asia, Australia, Canada, Connecticut, Delaware, Europe, Indiana, Maine, Maryland, Massachusetts, Michigan, New Hampshire, New Jersey, New York, Ohio, Pennsylvania, Rhode Island, Vermont; Office/Mail: 575 North Pennsylvania Street, Indianapolis, IN 46204; Phone: 1-888-407-0144; press # 2</FP>
                    <HD SOURCE="HD2">• Lincoln Fiduciary Hub</HD>
                    <FP SOURCE="FP-1">○ Jurisdiction for Central America, Kansas, Mexico, Nebraska, North Dakota, Oklahoma, South America, South Dakota, Texas; Office: 3800 Village Drive, Lincoln, NE 68501; Mail: P.O. Box 5444, Lincoln, NE 68505; Phone:1-888-407-0144; press # 3</FP>
                    <HD SOURCE="HD2">• Louisville Fiduciary Hub</HD>
                    <FP SOURCE="FP-1">○ Jurisdiction for Alabama, Kentucky, Mississippi, Tennessee, Puerto Rico, Virginia, Washington, DC, West Virginia; Office: 321 West Main Street, Ste 390, Louisville, KY 40202; Mail: P.O. Box 3487, Louisville, KY,40201; Phone:1-888-407-0144; press # 4</FP>
                    <HD SOURCE="HD2">• Manila Regional Office</HD>
                    <FP SOURCE="FP-1">○ Jurisdiction for Philippines; Office: U.S. Embassy, 1501 Roxas Boulevard, Pasay City, Philippines,1302; Mail: PSC 501, DPO AP 96515</FP>
                    <HD SOURCE="HD2">• Milwaukee Fiduciary Hub</HD>
                    <FP SOURCE="FP-1">○ Jurisdiction for Arkansas, Illinois, Iowa, Louisiana, Minnesota, Missouri, Wisconsin; Office: 5400 West National Avenue, Milwaukee, WI 53214; Mail: P.O. Box 14975, Milwaukee, WI 53214; Phone:1-888-407 0144; press # 5</FP>
                    <HD SOURCE="HD2">• Salt Lake City Fiduciary Hub</HD>
                    <FP SOURCE="FP-1">○ Jurisdiction for Alaska, Arizona, California, Colorado, Hawaii, Idaho, Montana, New Mexico, Nevada, Oregon, Utah, Washington, Wyoming; Office: 500 Foothill Drive, Salt Lake City, UT 84158; Mail: P.O. Box 58086, Salt Lake City, UT 84158; Phone:1-888-407-0144; press # 6</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-13846 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <SUBJECT>Joint Brain, Behavioral, and Mental Health and Medical Health (BBMH/MED) Scientific Merit Review Board, Notice of Meeting</SUBJECT>
                <P>The Department of Veterans Affairs (VA) gives notice under the Federal Advisory Committee Act, as amended, 5 U.S.C. Ch. 10, that a meeting of the Joint Brain, Behavioral, and Mental Health and Medical Health (BBMH/MED) Scientific Merit Review Board will be held July 13, 2026, from 3:00 p.m.-5:00 p.m. Eastern Standard Time (EST), via Microsoft Teams. The meeting will be open to the public from 3:00 p.m.-3:30 p.m. EST. The remainder of the meeting, from 3:30 p.m.-5:00 p.m. EST, will be closed to the public and used for scientific review and discussion, examination of, and reference to the research applications. Discussions will involve staff and consultant critiques of research proposals. Discussions will also cover the scientific merit of each proposal and the qualifications of the personnel conducting the studies, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy. Additionally, premature disclosure of research information could significantly obstruct implementation of proposed agency action regarding the research proposals. Therefore, portions of the Board meeting will be closed to the public in accordance with 5 U.S.C. 552b(c)(4), (6), and (9)(B).</P>
                <P>The objectives of the Board are to provide expert review of the scientific quality, budget, safety, and mission-relevance of investigator-initiated research applications submitted for VA merit review consideration and to offer advice for research program officials on program priorities and policies.</P>
                <P>The Board advises the Deputy Chief Research and Development Officer (Deputy CRADO) for Investigators, Scientific Review, and Management, and the Acting CRADO for the Office of Research and Development, on strategies, goals, and direction to support emerging issues and topics in Veteran health care through research, scientific and technical merit, and mission relevance. The Board does not consider grants, contracts, or other forms of extramural research.</P>
                <P>Members of the public may attend the open portion of the meeting from 3:00 p.m.-3:30 p.m. EST, via Microsoft Teams (in listen-only mode, as the time-limited agenda does not allow for public comment or presentations). To attend the open portion of the meeting, the public may dial the Microsoft Teams phone number (872-701-0185) and enter the meeting access code: 65958217#.</P>
                <P>
                    Written comments from members of the public should be sent to Michael R. Burgio, Ph.D., Designated Federal Officer, BBMH/MED, U.S. Department of Veterans Affairs, 810 Vermont Avenue NW, Washington, DC 20420, or to 
                    <E T="03">Michael.Burgio@va.gov,</E>
                     at least 5 days before the meeting. The written public comments will be shared with the Board members. The public may not attend the closed portion of the meeting.
                </P>
                <SIG>
                    <DATED>Dated: July 6, 2026.</DATED>
                    <NAME>Jelessa M. Burney,</NAME>
                    <TITLE>Federal Advisory Committee Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-13833 Filed 7-8-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>91</VOL>
    <NO>130</NO>
    <DATE>Thursday, July 9, 2026</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="42601"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P">Federal Communications Commission</AGENCY>
            <CFR>47 CFR Parts 1 and 64</CFR>
            <TITLE>Enhancing Know-Your-Upstream-Provider Requirements and Strengthening STIR/SHAKEN (Call Authentication Trust Anchor; Advanced Methods To Target and Eliminate Unlawful Robocalls); Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="42602"/>
                    <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                    <CFR>47 CFR Parts 1 and 64</CFR>
                    <DEPDOC>[WC Docket No. 17-97; CG Docket No. 17-59; FCC 26-32; FR ID 355060]</DEPDOC>
                    <SUBJECT>Enhancing Know-Your-Upstream-Provider Requirements and Strengthening STIR/SHAKEN (Call Authentication Trust Anchor; Advanced Methods To Target and Eliminate Unlawful Robocalls)</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Federal Communications Commission.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>In this document, the Federal Communications Commission (Commission) proposes steps to strengthen its robocall mitigation framework by enhancing Know-Your-Upstream-Provider (KYUP) requirements, improving oversight of voice service providers by the STIR/SHAKEN Governance Authority, raising caller ID attestation standards, and closing implementation gaps in STIR/SHAKEN implementation. Specifically, the Commission proposes establishing baseline KYUP information-collection, compliance review, verification, monitoring, and responsive-action requirements to ensure providers can identify and cut off bad-actor upstream providers. The Commission also proposes measures to expand the Governance Authority's vetting, enforcement, and reporting responsibilities to prevent misuse of STIR/SHAKEN certificates and to remove noncompliant providers from the authentication ecosystem. The Commission further proposes clarifying and strengthening STIR/SHAKEN attestation rules, including codifying attestation levels, defining improper attestations, and specifying permissible mechanisms for verifying number-to-customer associations. Additionally, the Commission proposes and seeks comment on additional steps to close caller ID authentication gaps, such as refining provider definitions, reconsidering exemptions, requiring providers serving end users to assign STIR/SHAKEN attestations, and ensuring calls maintain authentication information. The Commission also seeks comment on special circumstances, including addressing issues with foreign-originated calls.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Comments are due on or before August 10, 2026 and reply comments are due on or before September 8, 2026.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>Pursuant to §§ 1.415 and 1.419 of the Commission's rules, 47 CFR 1.415, 1.419, interested parties may file comments and reply comments identified by WC Docket No. 17-97 and CG Docket No. 17-59 by any of the following methods:</P>
                        <P>
                            • 
                            <E T="03">Electronic Filers:</E>
                             Comments may be filed electronically using the internet by accessing the Electronic Comment Filing System (ECFS): 
                            <E T="03">https://www.fcc.gov/</E>
                            ecfs. See 
                            <E T="03">Electronic Filing of Documents in Rulemaking Proceedings,</E>
                             63 FR 24121 (1998).
                        </P>
                        <P>
                            • 
                            <E T="03">Paper Filers:</E>
                             Parties who choose to file by paper must file an original and one copy of each filing.
                        </P>
                        <P>
                            • Filings can be sent by hand or messenger delivery, by commercial courier, or by the U.S. Postal Service. 
                            <E T="03">All filings must be addressed to the Secretary, Federal Communications Commission.</E>
                        </P>
                        <P>• Hand-delivered or messenger-delivered paper filings for the Commission's Secretary are accepted between 8:00 a.m. and 4:00 p.m. by the FCC's mailing contractor at 9050 Junction Drive, Annapolis Junction, MD 20701. All hand deliveries must be held together with rubber bands or fasteners. Any envelopes and boxes must be disposed of before entering the building.</P>
                        <P>• Commercial courier deliveries (any deliveries not by the U.S. Postal Service) must be sent to 9050 Junction Drive, Annapolis Junction, MD 20701.</P>
                        <P>• Filings sent by U.S. Postal Service First-Class Mail, Priority Mail, and Priority Mail Express must be sent to 45 L Street NE, Washington, DC 20554.</P>
                        <P>
                            • 
                            <E T="03">Accessible formats.</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), send an email to 
                            <E T="03">fcc504@fcc.gov</E>
                             or call the Consumer and Governmental Affairs Bureau at (202) 418-0530 (voice).
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Chris Laughlin of the Wireline Competition Bureau at (202) 418-2193 or 
                            <E T="03">Chris.Laughlin@fcc.gov.</E>
                             For additional information concerning the Paperwork Reduction Act proposed information collection requirements contained in this document, email 
                            <E T="03">PRA@fcc.gov</E>
                             or contact Nicole Ongele at (202) 418-2991.
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        This is a summary of the Commission's Further Notice of Proposed Rulemaking (
                        <E T="03">FNPRM</E>
                        ) in WC Docket No. 17-97 and CG Docket No. 17-59, FCC 26-32, adopted on May 20, 2026 and released on May 21, 2026. The full text of this document is available online at: 
                        <E T="03">https://docs.fcc.gov/public/attachments/FCC-26-32A1.pdf.</E>
                    </P>
                    <P>
                        <E T="03">Paperwork Reduction Act Analysis:</E>
                         The 
                        <E T="03">FNPRM</E>
                         may contain proposed new and revised information collection requirements. The Commission, as part of its continuing effort to reduce paperwork burdens, invites the general public and the Office of Management and Budget (OMB) to comment on the information collection requirements described in this document, as required by the Paper Reduction Act of 1995, Public Law 104-13. In addition, pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, see 44 U.S.C. 3506(c)(4), we seek specific comment on how we might further reduce the information collection burden for small business concerns with fewer than 25 employees.
                    </P>
                    <P>
                        <E T="03">Providing Accountability Through Transparency Act:</E>
                         Consistent with the Providing Accountability Through Transparency Act, Public Law 118-9, a summary of this document will be available on 
                        <E T="03">https://www.fcc.gov/proposed-rulemakings.</E>
                    </P>
                    <P>
                        <E T="03">Ex Parte Rules:</E>
                         The proceeding the 
                        <E T="03">FNPRM</E>
                         initiates shall be treated as a “permit-but-disclose” proceeding in accordance with the Commission's 
                        <E T="03">ex parte</E>
                         rules. Persons making 
                        <E T="03">ex parte</E>
                         presentations must file a copy of any written presentation or a memorandum summarizing any oral presentation within two business days after the presentation (unless a different deadline applicable to the Sunshine period applies). Persons making oral 
                        <E T="03">ex parte</E>
                         presentations are reminded that memoranda summarizing the presentation must (1) list all persons attending or otherwise participating in the meeting at which the 
                        <E T="03">ex parte</E>
                         presentation was made, and (2) summarize all data presented and arguments made during the presentation. If the presentation consisted in whole or in part of the presentation of data or arguments already reflected in the presenter's written comments, memoranda or other filings in the proceeding, the presenter may provide citations to such data or arguments in his or her prior comments, memoranda, or other filings (specifying the relevant page and/or paragraph numbers where such data or arguments can be found) in lieu of summarizing them in the memorandum. Documents shown or given to Commission staff during 
                        <E T="03">ex parte</E>
                         meetings are deemed to be written 
                        <E T="03">ex parte</E>
                         presentations and must be filed consistent with § 1.1296(b) of the Commission's rules. In proceedings governed by § 1.49(f) of the Commission's rule or for which the Commission has made available a method for electronic filing, written 
                        <E T="03">ex parte</E>
                         presentations and memoranda 
                        <PRTPAGE P="42603"/>
                        summarizing oral 
                        <E T="03">ex parte presentations,</E>
                         and all attachments thereto, must, when feasible, be filed through the electronic comments filing system available for that proceeding, and must be filed in their native format (
                        <E T="03">e.g.,</E>
                         .doc, .xml, .ppt., searchable .pdf). Participants in this proceeding should familiarize themselves with the Commission's 
                        <E T="03">ex parte</E>
                         rules.
                    </P>
                    <HD SOURCE="HD1">Synopsis</HD>
                    <HD SOURCE="HD1">I. Discussion</HD>
                    <P>Commission measures to stop unlawful and fraudulent calls are only as effective as the voice service providers that implement them. Numbering rules assume providers will use telephone numbers responsibly. The STIR/SHAKEN framework is built on an expectation that providers will authenticate calls and do so with a proper attestation. The value of the Robocall Mitigation Database (RMD) is reliant on providers following their described robocall mitigation programs and only accepting calls from providers with a filing that appears in the RMD. Tracebacks only work if providers respond to traceback requests. Know-your-customer (KYC) requirements are only effective if providers meaningfully vet their customers. The call blocking rules depend on providers actually blocking calls when permitted or required. And the utility of some burgeoning call-branding solutions can be dependent on the effectiveness of STIR/SHAKEN and on the role providers play in verifying the identity of callers. But when voice service providers fail to fulfill these responsibilities, these systems can break down, and illegal calls can find their way to consumers.</P>
                    <P>We propose a number of actions designed to increase voice service providers' accountability in fulfilling these obligations. First, we propose steps aimed at removing voice service providers that enable illegal calls from the voice ecosystem. Second, we propose to raise the bar for STIR/SHAKEN attestations to ensure that voice service providers are applying the correct attestations to calls. Third, we propose to close certain STIR/SHAKEN implementation loopholes to ensure ubiquitous and consistent deployment of STIR/SHAKEN on IP networks. Fourth, we address special circumstances related to TRS providers, foreign-originated calls, and public safety. We also propose and seek comment on related implementation considerations. We believe these proposed actions will not only enhance the effectiveness of STIR/SHAKEN, but will directly and indirectly improve the efficacy of the Commission's other anti-robocall measures, thereby advancing the Commission's ultimate goal to restore trust in voice communications. As the Commission continues its efforts to combat illegal robocalls through STIR/SHAKEN implementation, the RMD, numbering accountability rules, KYC requirements, and now stronger know-your-upstream-provider (KYUP) standards, we are committed to ensuring that rules designed to protect consumers from illegal calls do not inadvertently create new risks by mandating the collection, retention, and sharing of sensitive business and personal data without corresponding safeguards.</P>
                    <HD SOURCE="HD2">A. Cutting Off Providers That Enable Illegal Calls</HD>
                    <P>Whether they actively collaborate with fraudsters, turn the other way when bad actors use their networks or services to transmit illegal calls or defraud consumers, or simply fail to implement policies and procedures to fulfill their regulatory obligations to stop such nefarious activity, voice service providers that evade or ignore our rules undermine trust in the voice network and the effectiveness of tools designed to combat illegal calls. Providers and other industry stakeholders have been well positioned to identify “bad actor providers” and take rapid action to address them. The Commission established a flexible KYUP requirement that both empowers and obligates providers to identify bad actor providers and keep them from getting illegal calls onto the United States voice network. Similarly, the STIR/SHAKEN Governance Authority was designed to maintain trust in the STIR/SHAKEN framework by setting policies and procedures that govern which providers are authorized to be a part of the STIR/SHAKEN ecosystem. Despite these mechanisms, many bad actor providers remain.</P>
                    <P>We propose and seek comment on measures designed to improve how providers' KYUP obligation and the STIR/SHAKEN Governance Authority serve to excise bad actor providers from the voice network and deter them from establishing new operations to get back in. Although we are aware that bad actors will continue to look for new ways to commit fraud, we believe these actions will create friction that substantially undercuts the ability of bad actor providers to profit from transmitting illegal calls. Specifically, we believe our proposals will disincentivize bad actor providers from attempting to gain access to the United States voice network by increasing both the costs they must incur to appear legitimate, and the chances that their deceptive schemes will be discovered through ongoing monitoring practices that may result in their expulsion from the United States voice network. We seek comment on this assessment and on the potential impact of the requirements we propose.</P>
                    <HD SOURCE="HD3">1. Establishing Specific KYUP Requirements</HD>
                    <P>The existing KYUP rule gives voice service providers the flexibility to use the best methods to know their upstream providers and prevent them from transmitting illegal calls. But those benefits will only materialize if providers actually take accountability and adopt meaningful measures to know their upstream providers and act on that knowledge. Below we propose to define “upstream” and “downstream” to codify the relationships between providers, particularly as it relates to the application of any existing and future KYUP requirements. Consistent with our description there, a non-facilities-based provider on the origination side of a call path is responsible for conducting KYUP regarding the providers to which it resells service, while a non-facilities-based provider on the termination side of a call path is responsible for conducting KYUP regarding the providers from which it purchases service. Thus far, the Commission has declined to require that providers adopt specific KYUP measures, opting to allow them to determine the best means to fulfill that responsibility. However, we believe that for some providers, the incentive to enter into business with other providers to drive revenue growth deters them from instituting even the most basic practices to evaluate their upstream providers. Other providers may not have implemented baseline practices because they do not take their KYUP obligations seriously. Indeed, record evidence suggests that some providers are failing to take action to cut off bad actor providers even though the universe of bad actor providers appears identifiable and even when the evidence against a particular provider is clear. Although stakeholders disagree on exactly what should be done to address providers' lax KYUP practices, many agree that better practices—and Commission action to achieve them—are needed.</P>
                    <P>
                        In light of this evidence, we now believe it is necessary to establish certain baseline measures that all voice service providers must follow to help ensure the upstream providers they serve are legitimate and responsible entities that are unlikely to be the 
                        <PRTPAGE P="42604"/>
                        source of illegal calls. Specifically, we propose five categories of baseline measures that providers must follow to fulfill their obligation to know their upstream provider: information collection, compliance review, information verification, monitoring, and responsive action. We developed these categories and the included baseline measures using a variety of Commission and private-sector resources and believe this framework is the logical outgrowth of the types of KYUP practices that responsible voice service providers use today. The resources we relied on include the proposals in the 
                        <E T="03">KYC FNPRM,</E>
                         91 FR 30596 (May 26, 2026), prior enforcement determinations, the caller ID authentication best practices released by the Wireline Competition Bureau (Bureau) and the associated best practices adopted by the North American Numbering Council (NANC) Call Authentication Trust Anchor (CATA) Working Group, the i3 Forum Know Your Customer/Know Your Traffic Code of Conduct, and best practices identified by stakeholders in the 
                        <E T="03">Call Branding FNPRM,</E>
                         90 FR 56101 (Dec. 5, 2025) record. We seek comment on these categories and baseline measures. We also propose and seek comment on related issues, including appeals, barriers to performing KYUP responsibilities, use of third parties, compliance and recordkeeping responsibilities, implementation costs and cost recovery, and alternative approaches to various aspects of our proposed KYUP scheme.
                    </P>
                    <P>
                        We propose triggers for when a voice service provider must perform these KYUP requirements. Specifically, we propose that they must do so: (a) before entering into a service agreement with a new upstream provider; (b) before renewing or renegotiating an agreement with an upstream provider that has an existing service agreement; and (c) at any other time the voice service provider finds, receives, or is made aware of information or evidence concerning an upstream provider, such as through the monitoring practices we propose. We seek comment on these triggers, including whether we should set more specific triggers for performing the KYUP requirements. Below we propose to require that the KYUP rules go into effect the later of 12 months after 
                        <E T="04">Federal Register</E>
                         publication of a Report and Order adopting the rules or 30 days after approval by the Office of Management and Budget (OMB) for rules that contain new or modified information collections subject to review under the Paperwork Reduction Act (PRA). Accordingly, by the time the rules go into effect, providers would need to have processes and procedures in place to perform the KYUP requirements in accordance with the triggers. Additionally, we propose to require that, within six (6) months 
                        <E T="03">after</E>
                         the rules go into effect, a provider must perform a one-time information collection, compliance review, and information verification KYUP review for all upstream providers with which it has a service agreement at the time the rules we adopt go into effect if the provider has not already performed the KYUP requirements for an upstream provider under the proposed triggers above.
                    </P>
                    <P>
                        We acknowledge that the KYUP requirements we propose above may be considered more prescriptive than the approach suggested in our recent 
                        <E T="03">KYC FNPRM,</E>
                         and we believe this is warranted. As we noted above, voice service providers are the first line of defense with respect to many of the Commission's and private sector's robocall mitigation measures. When bad actor providers are in the ecosystem, those measures often fail, and so we believe it is important to ensure that voice service providers follow robust baseline KYUP practices. We also believe robust KYUP practices are more feasible for providers to follow than more stringent KYC practices for retail, small business, and enterprise end users because there are far fewer providers than there are end users. In May 2025, the Commission's Office of Economics and Analytics reported that as of June 2024, “there were 18 million end-user switched access lines in service, 65 million interconnected VoIP subscriptions, and 388 million mobile subscriptions, for a total of 471 million retail voice telephone service connections in the United States.” Conversely, as of April 21, 2026 there are only 10,872 voice providers with filings in the Commission's Robocall Mitigation Database, and we believe each provider only directly accepts traffic from a relatively small subset of these providers. Additionally, we believe that voice service providers will have a heightened awareness of the importance of responding to KYUP requests to ensure their calls go through than would retail and small businesses end users that may be unfamiliar with KYC and KYUP requirements that apply in the communications industry.
                    </P>
                    <P>We believe these measures will realign provider incentives and further empower them to be another “cop on the beat” stopping bad actor providers from getting illegal calls onto the voice network. The measures are meant to target upstream providers to which no reasonable voice service provider would provision service and ensure that all voice service providers are held to that same standard. We also believe that specifying KYUP requirements will provide a clearer foundation on which to hold providers accountable; providers that fail to take these obligations seriously may be subject to enforcement action. The measures we propose are not intended to be exhaustive, and if adopted, voice service providers would continue to have both the flexibility and an obligation to implement additional practices to respond to new tactics by bad actor providers in order to satisfy their obligation to prevent their networks and services from being used to transmit illegal calls.</P>
                    <P>
                        <E T="03">Strengthening the general KYUP requirement.</E>
                         As the foundation for our proposed KYUP requirements, we propose to revise the baseline KYUP requirement in § 64.1200(n)(5) of our rules to establish an even more stringent obligation on voice service providers to prevent the transmission of illegal calls from upstream providers. Specifically, we propose to require that each voice service provider take affirmative, effective measures to prevent an upstream provider from using its network or services to transmit illegal calls, including knowing its upstream provider. The proposed revised language focuses on the illegality of calls rather than traffic (consistent with how our rules typically apply) and cuts the “high volume of illegal traffic” limitation in the current rule to require that providers prevent all illegal calls. We also believe our proposed changes make clear our intent to apply this rule to all voice service providers, including both facilities-based providers and non-facilities-based providers. We seek comment on this proposal and analysis.
                    </P>
                    <P>
                        <E T="03">KYUP information collection.</E>
                         We propose to require that voice service providers collect directly from upstream providers, using mechanisms of their own choosing, the following information or an explanation for why the upstream provider cannot produce this information:
                    </P>
                    <P>• General business information, including:</P>
                    <P>
                        ○ legal business name and supporting records (
                        <E T="03">e.g.,</E>
                         government record, government identification, lease, utility statement, search result from a government website, or report from a legitimate private database that validates company information);
                    </P>
                    <P>
                        ○ any prior business names or trade names (DBAs) the company has used in the last three years;
                        <PRTPAGE P="42605"/>
                    </P>
                    <P>○ a physical address that is a real place of business for the upstream provider and is not a virtual address, shared office location without a dedicated suite or floor, P.O. Box, mail forwarding service, hosted server location, registered agent, or address shared by multiple unrelated or purportedly unrelated businesses; and</P>
                    <P>○ contact information, including a business telephone number and email address;</P>
                    <P>• Financial information, including: billing address, forms of payment, financial institution, and account information;</P>
                    <P>• Internet commercial presence information, such as website, social media, or apps;</P>
                    <P>• Ownership and affiliate information, including:</P>
                    <P>○ information about human principals, owners, and company leadership (including ultimate beneficial owners and authorized business representatives), including their name, title, business telephone number, business email address, work address, country of residence, citizenship, and copies of government issued identification;</P>
                    <P>○ information about the company's parents, affiliates, and subsidiaries, including their business names, trade names (DBAs), place of incorporation, and principal places of business;</P>
                    <P>○ names, addresses (including country), email addresses, and ownership stake for all individuals with 10% or more direct or indirect ownership of the company; and</P>
                    <P>○ whether or not the provider or its parents, affiliates, subsidiaries, principals, owners, or leadership, and other companies where any such persons have served as a principal, owner, or leader, have been the subject of any criminal or regulatory investigations or actions in the past five years and the nature of such investigations or actions;</P>
                    <P>• Operational information, including:</P>
                    <P>○ place of formation and corporate formation records, including proof of good standing;</P>
                    <P>○ location of its principal operations, how long the company has been operating, and whether the company has any foreign ownership or management;</P>
                    <P>○ business registration number in its jurisdiction (such as federal or state Employer Identification Numbers (EINs) for United States providers and the foreign-equivalents for foreign providers); and</P>
                    <P>○ registered United States agent (if the provider has one);</P>
                    <P>• Service information, including:</P>
                    <P>○ information about the nature of the upstream provider's operations, including the types of services it offers, the types of customers it serves or intends to serve, and whether it relies on non-internet Protocol (IP) technology—the TRACED Act, and the Commission's rules implementing it, use the general term “non-internet protocol” to capture networks that use types of technology other than IP; such technology includes time-division multiplexing (TDM) technology, which often uses the Signaling System No. 7 (SS7) protocol instead of Session Initiation Protocol (SIP) ; and</P>
                    <P>○ whether another voice service provider has refused or discontinued service to the upstream provider.</P>
                    <P>We believe that this is the basic amount of information necessary for a provider to be able to know their upstream providers. We also believe this information will help providers determine if an upstream provider is a foreign entity. Are these views correct? Is there additional information we should require providers to obtain? For instance, should we require that providers obtain photos of certain individuals the upstream provider identifies with their government-issued identification? Is there any information listed above that providers should not be required to obtain? If not, why not? We believe it is beneficial to require providers to obtain this information directly from upstream providers because upstream providers are in the best position to supply this information. It may also serve to spur upstream providers to complete necessary steps to establish their business while deterring bad actor providers that may be disincentivized from taking the steps necessary to appear legitimate. Do commenters agree? We seek comment on whether any such information constitutes sensitive business or personal information, and if so, what safeguards we can implement to prevent the misuse of such information. We recognize that some of this information may be duplicative of information voice service providers must submit in the RMD, but to the extent providers would not collect this information directly from new upstream providers anyway, we think requiring providers to obtain this information will allow them to cross-check the information with the RMD to identify any inconsistencies. We are exploring whether some entities are establishing dummy filings in the RMD that bad actors can use to quickly start transmitting unlawful traffic, and which may contain false or unverifiable information and are not properly updated. We intend to evaluate potential improvements to the RMD in a future proceeding.</P>
                    <P>
                        <E T="03">KYUP compliance review.</E>
                         We propose to require that voice service providers perform due diligence of upstream providers' compliance with Commission rules related to the provision of service by:
                    </P>
                    <P>• Confirming the upstream provider has a filing in the RMD (providers can check the RMD in three ways: (1) searching the database by filer or keyword; (2) downloading a .csv file that lists the filings in the database; or (3) accessing the database using the application program interface (API)) and reviewing the filing (including the robocall mitigation plan) to generally assess whether it is complete and compliant with Commission rules—although we do not propose to specify exact requirements for this assessment, we believe providers should check whether a filing includes all required information, such as: principals, parents, affiliates, and subsidiaries, including, at a minimum, at least one natural person principal; operating company number (OCN) if the upstream provider has certified to complete or partial STIR/SHAKEN implementation (as an OCN is required to get a Service Provider Code (SPC) token to implement STIR/SHAKEN); a valid exemption and a detailed basis for claiming the exemption if the upstream provider certifies to less than complete STIR/SHAKEN implementation; and a robocall mitigation plan that describes the upstream provider's robocall mitigation program, including KYC and KYUP measures;</P>
                    <P>• Confirming the upstream provider has obtained an SPC token if it certified in its RMD filing that it has fully or partially implemented STIR/SHAKEN;</P>
                    <P>• Determining whether the upstream provider appears on the Foreign Adversary Control System or the Covered List;</P>
                    <P>• Determining whether the upstream provider has been subject to a Commission action revoking a Commission license; and</P>
                    <P>• Determining whether the upstream provider has been the subject of any other final or preliminary Commission enforcement actions—this includes Forfeiture Orders, Consent Decrees, Final Determination Orders, Final RMD Removal Orders, Cease-and-Desist Letters, and Notices of Apparent Liability;</P>
                    <P>
                        In addition to these mechanisms, we believe that providers should evaluate an upstream provider's traceback history, including whether the upstream provider was the source of any tracebacks or failed to respond to any 
                        <PRTPAGE P="42606"/>
                        traceback requests, and we seek comment on how easily providers can obtain this information. Additionally, we believe that providers should try to ascertain, beyond just a general provision in a contract, whether an upstream provider actually has mechanisms in place to ensure its own customers, upstream providers, clients, employees, and contractors comply with federal and state laws and regulations concerning unlawful calls, including any KYC and KYUP requirements established by the Commission, and we seek comment on how and the extent to which providers can do this. We also seek comment on whether and how providers may determine whether a provider has been subject to numbering restrictions by the North American Numbering Plan Administrator (NANPA). By numbering restrictions, we mean that the upstream provider has been prohibited from accessing numbers directly from the NANPA, has had its access to numbers suspended, or has had numbers reclaimed.
                    </P>
                    <P>We believe this compliance review is a sufficient baseline that providers can use to evaluate whether upstream providers are following Commission regulatory obligations without unnecessarily burdening providers with obligations that are inflexible or require comprehensive compliance reviews. We seek comment on these requirements and this assessment. Should voice service providers be required to perform more or less detailed compliance reviews? Should they confirm that upstream providers have an FCC Form 499 on file with the Commission? Should we require that contracts between voice service providers and upstream providers specifically address that the upstream providers will follow KYUP and KYC requirements established by the Commission, rather than just generic statements that the upstream providers will comply with all laws and regulations?</P>
                    <P>
                        <E T="03">KYUP information verification.</E>
                         We propose to require that voice service providers conduct at least a basic level of due diligence to verify the validity and authenticity of an upstream provider, the information voice service providers obtain from or about an upstream provider, and the upstream provider's explanation for any information it could not produce, including:
                    </P>
                    <P>• Confirming any telephone numbers and email addresses are active;</P>
                    <P>• Participating in a verbal communication with one or more natural person principals, owners, or company leaders;</P>
                    <P>• Conducting general research to identify risk factors or contradictory information, such as:</P>
                    <P>○ whether the physical address provided by the upstream provider represents a real place of business associated with the provider and is not a virtual address, shared office location without a dedicated suite or floor, P.O. Box, mail forwarding service, hosted server location, or an address shared by multiple unrelated or purportedly unrelated businesses;</P>
                    <P>○ whether there is contradictory information concerning the upstream provider's place of business, such as evidence the company is based outside the United States, including whether the company's IP address is associated with a foreign country or otherwise does not match the location information provided;</P>
                    <P>○ whether the principals, owners, and leadership of the upstream provider exist as natural persons;</P>
                    <P>○ whether there is any information that contradicts an upstream provider's claims about prior criminal or regulatory investigations or actions;</P>
                    <P>○ whether there is other evidence that raises questions about the upstream provider's legitimacy or reputation, such as a lack of digital presence for a purportedly established company; and</P>
                    <P>○ whether the upstream provider is owned by, controlled by, or subject to the jurisdiction or direction of a foreign adversary;</P>
                    <P>• Reviewing the upstream provider's internet commercial presence information to identify risk factors or contradictory information, such as:</P>
                    <P>
                        ○ excessive spelling and grammatical errors, being created recently, apparent copying of another company's website, apparently fake customer reviews, or use of fake photos for leadership and listed employees (
                        <E T="03">e.g.,</E>
                         stock photos, potentially AI-generated photos, or photos of persons with no relationship to the provider); and
                    </P>
                    <P>○ whether it contains information that contradicts the information supplied to the provider, including, but not limited to, different contact information, different leadership, or an inconsistent description of the nature of the services and types of customers served;</P>
                    <P>• Conducting a basic comparative analysis of the information to identify inconsistencies in the information or consistencies with information concerning other upstream providers, such as:</P>
                    <P>○ different business names, addresses, contact information, email addresses or website domains, and individuals involved with the company;</P>
                    <P>○ similarities with other current or former upstream providers purportedly operating as unrelated entities, which may indicate the upstream provider is replacing a provider whose calls were being scrutinized or blocked; and</P>
                    <P>
                        • Evaluating an upstream provider's financial information to identify risk factors, such as untraceable forms of payment (
                        <E T="03">e.g.,</E>
                         cryptocurrency or prepaid credit cards).
                    </P>
                    <P>We believe that this level of due diligence sufficiently balances the need for providers to evaluate the information the upstream provider supplied without placing unreasonably burdensome or inflexible baseline requirements for that evaluation. We seek comment on these requirements and this assessment. Should we require providers to conduct more or less due diligence? Should we require providers to take additional steps to verify the identities of natural person principals, owners, and/or leadership, such as checking identity verification or reputation databases? Should we require credit checks?</P>
                    <P>
                        <E T="03">KYUP monitoring.</E>
                         To protect against bad actor providers who successfully circumvent initial KYUP vetting, we propose to require that voice service providers implement the following baseline KYUP monitoring obligations:
                    </P>
                    <P>• Regularly checking the upstream provider's compliance with Commission rules related to the provision of service, consisting of whether the upstream provider no longer has a filing in the RMD, has had its SPC token revoked, has been added to the Foreign Adversary Control System or the Covered List, has had a Commission license revoked, or has become the subject of any other Commission enforcement actions;</P>
                    <P>• Using call analytics on an ongoing basis to identify illegal or suspect calls or call patterns from each upstream provider, including whether the upstream provider is transmitting calls from a further upstream provider that the voice service provider knows no longer has a filing in the RMD, has had its SPC token revoked, appears on the Foreign Adversary Control System or Covered List, has had a Commission license revoked, or has been subject of a Commission enforcement action that denies its ability to provision voice service;</P>
                    <P>• Evaluating on a timely basis information or evidence it finds, receives, or is made aware of that an upstream provider is transmitting illegal calls, failing to authenticate calls, or authenticating calls with improper attestations;</P>
                    <P>
                        • Evaluating on a timely basis whether any information or evidence it 
                        <PRTPAGE P="42607"/>
                        finds, receives, or is made aware of presents inconsistencies with other KYUP information obtained from or about the upstream provider, such as that:
                    </P>
                    <P>○ the upstream provider or its employees are operating outside the United States, or its calls are originating outside the United States when it claimed it is a domestic provider;</P>
                    <P>○ the upstream provider's calls are originating in the United States when it claimed it is a foreign provider;</P>
                    <P>○ the upstream provider is providing different types of service or serving different types of customers than what was described;</P>
                    <P>○ the upstream provider's calls are sent over non-IP technology when the upstream provider did not specify it uses such technology; and</P>
                    <P>• Evaluating on a timely basis any other new information or evidence it finds, receives, or is made aware of concerning the upstream provider's reputation, such as a refusal or discontinuance of service by another provider.</P>
                    <P>We seek comment on each of these proposed requirements and whether we should specify additional KYUP monitoring obligations. For instance, should we specify the type of call analytics information providers must implement and evaluate? For example, the I3 Forum suggests that providers should implement the following call analytics measures: short call duration percentage; average call duration; answer seizure ratio (ASR); the percentage of call attempts blocked due to an improper CLI (invalid, unallocated, on a DNO list etc.); delivery receipt ratio (DLR); ratio of long code Sender IDs relative to short code Sender IDs; and ratio of long code Sender IDs relative to alphanumeric Sender IDs. We note that Commission rules require providers to describe any call analytics they use to identify and block illegal traffic, including whether they use any third-party call analytics providers and the names of those providers. Should we require that providers monitor when certificates have been revoked and not just SPC tokens? Should we direct providers to require, such as through interconnection agreements, that upstream providers update any information the upstream provider supplied within a certain amount of time of any change, such as 10 business days? Should we establish a more specific obligation for providers to proactively monitor upstream providers? Are there any obligations listed above that we should not require providers to follow? We also seek comment on whether we should set specific monitoring timelines, rather than the “regularly,” “ongoing,” and “timely basis” proposed requirements.</P>
                    <P>
                        <E T="03">KYUP responsive action.</E>
                         We propose to require that voice service providers perform a holistic, totality-of-the-circumstances evaluation of each upstream provider based on the information collection, information verification, compliance review, and monitoring measures described above and implement measures to refuse or discontinue service:
                    </P>
                    <P>• When the results do not form an objectively reasonable basis for concluding that the upstream provider is a valid and authentic entity;</P>
                    <P>• When the results form an objectively reasonable basis for concluding that an upstream provider is likely to use or is using the network or services of the provider with the KYUP obligation to transmit illegal calls or enable the transmission of illegal calls;</P>
                    <P>• When the upstream provider does not have a filing in the RMD, transmits calls in IP but does not have an SPC token, appears on the Foreign Adversary Control System or Covered List, has had a Commission license revoked, or has been the subject of any other Commission enforcement actions that deny its ability to provision voice service—we believe that providers are already obligated to refuse or discontinue services to upstream providers who have not fulfilled compliance obligations necessary to provision service or whose authority to provide service by Commission action has been revoked, but we believe that establishing a rule will more clearly put providers on notice of this obligation; and</P>
                    <P>• When the provider finds, receives, or is made aware that an upstream provider does not have mechanisms in place to ensure its customers, upstream providers, clients, employees, and contractors comply with federal and state laws and regulations concerning unlawful calls, including any KYC and KYUP requirements established by the Commission.</P>
                    <P>We propose an objectively reasonable standard to prevent subjective applications where a provider refuses or discontinues service for anticompetitive purposes and where a provider fails to refuse or discontinue service when a reasonable provider would do so. To support providers taking responsive action, we propose that providers will receive a safe harbor from liability under the Act or Commission rules for objectively reasonable decisions to refuse or discontinue service, and seek comment on whether we should and have the authority to expand the safe harbor to better spur providers to take action. We seek comment on our proposal and whether it would serve our goal to remove bad actor providers from the voice network. What is the risk that providers would abuse their KYUP obligations for anticompetitive purposes? Are there other reasons we should require providers to refuse or discontinue service? Should we permit targeted call blocking based on providers' evaluations in certain circumstances, and if so, what circumstances? We also seek comment on potential economic or operational costs that could result if a provider refuses or discontinues service to valid and authentic upstream providers that are not in fact an actual or likely source of illegal calls due to a misapplication of the KYUP requirements.</P>
                    <P>We seek comment on whether our proposed approach will deter upstream providers from evading these requirements. Should we set a specific standard for when an upstream provider is using or likely to use the network or services of the provider with the KYUP obligation to transmit illegal calls or enable the transmission of illegal calls? Will these requirements successfully deter situations where bad actor providers create multiple shell providers, sometimes in multi-level arrangements, to try to avoid scrutiny by downstream providers? Will it address upstream providers that use traffic management techniques, such as mixing legal calls with illegal calls or transmitting illegal calls for short periods of time on a repeated but occasional basis? Should we set a requirement to discontinue service based on percentages of calls within certain timeframes that are presumptively illegal based on call analytics? If so, what should those percentages and timeframes be? Are there other standards we should set to address traffic management practices to evade our proposed requirements?</P>
                    <P>
                        As part of this requirement, we propose to require that voice service providers document their decisions to refuse or discontinue service—including their findings, supporting documents, and conclusions—and provide this information, or a summary thereof, in a notice to the upstream provider. We propose to require that providers deliver the notice to an upstream provider five (5) business days prior to discontinuing service. We do not believe a timeline is necessary for when a provider declines to provide service so long as a notice is delivered. We do not propose to prohibit providers from accepting new information or explanations from upstream providers and reconsidering 
                        <PRTPAGE P="42608"/>
                        their decisions. We seek comment on these proposals and views. Should we prohibit providers from counseling upstream providers on how to resolve issues? Should we require upstream providers that receive this notice to notify their customers of the forthcoming service discontinuance?
                    </P>
                    <P>We seek comment on how quickly a voice service provider must complete evaluations and take responsive action when it finds, receives, or is made aware of information or evidence concerning an upstream provider, such as through monitoring practices. Should we require that providers complete evaluations and take responsive action as soon as feasible and no later than 30 days after finding, receiving, or being made aware of information or evidence? Does that time period adequately balance the need to stop illegal calls quickly with giving providers sufficient time to conduct evaluations and take responsive action? How much time should providers permit upstream providers to respond to any concerns?</P>
                    <P>
                        <E T="03">Remedies.</E>
                         We believe that to the extent providers dispute whether a decision to refuse or discontinue service based on KYUP information is erroneous that they are positioned to remedy the disputes themselves. We seek comment on this belief. We nevertheless also seek comment on whether we should establish specific avenues for providers to remedy such disputes. We also seek comment on the costs associated with dispute resolution.
                    </P>
                    <P>
                        <E T="03">Barriers to performing KYUP responsibilities.</E>
                         We do not believe there are meaningful barriers to voice service providers performing the proposed KYUP requirements and we seek comment on this view. Because providers would obtain the required information directly from upstream providers, we do not believe there are barriers to obtaining that information. We believe providers have the means to conduct compliance reviews and monitoring using information from readily available public sources and will find, receive, or be made aware of information or evidence for monitoring purposes from its own call analytics tools and monitoring practices, the ITG, the Governance Authority, the Commission and other federal agencies, state entities (
                        <E T="03">e.g.,</E>
                         state Attorneys General), and other voice service providers. The proposed verification process would require fairly basic due diligence and we do not believe it would pose an unmanageable responsibility. Is there certain compliance information that providers would be unable to easily obtain, such as an upstream provider's traceback history? Are all voice service providers in the call path able to obtain information about an upstream provider's attestation practices? What about number access, license, and SPC token revocation information? Should we take steps to facilitate any necessary information sharing? Do we need to revise our rules implementing Section 222's privacy protections to allow certain information sharing? Are there any privacy or competitive concerns with facilitating sharing of the information described above, such as potential sharing of sensitive personal or business information, and how might any such concerns be mitigated? Should we find that sharing of aggregated data be explicitly permitted? Would there be particular challenges for small providers in complying with our proposed KYUP obligations, and if so, how should we reduce the burden for such providers? Are there alternatives to the proposed information collection, compliance review, information verification, and monitoring obligations that would allow small providers flexibility to identify bad actors?
                    </P>
                    <P>We also seek comment on any barriers to voice service providers refusing or discontinuing service. Are providers prevented from refusing service under federal or state laws or regulations in certain circumstances? We believe that most contracts between voice service providers include broad service discontinuance provisions that may be triggered by violation of applicable laws, and thus we believe that the discontinuance reasons we propose would be consistent with industry practice. Is this belief correct?</P>
                    <P>
                        <E T="03">Use of third-party KYUP services.</E>
                         We propose to allow voice service providers to use third-party services to conduct some or all of their KYUP obligations. We believe that allowing providers to use third-party KYUP services may help reduce any costs that result from the KYUP requirements we propose, including for small providers, and we seek comment on the costs of these services relative to providers performing KYUP obligations themselves. We also believe that third-party services will be able to develop into information clearinghouses as they collect information about a wide number of voice service providers in the ecosystem and use that information to inform their KYUP determinations for all the providers they work with. We seek comment on whether we should designate one or more specific entities to be an information clearinghouse and require providers to use that entity for some or all the information they must obtain, and if so, which third parties we should select. Should we require providers to use the Global Legal Entity Identifier System (GLEIS) to obtain certain information? While we propose to allow the use of third parties, we believe that the obligation to properly fulfill KYUP obligations should remain with providers. This, we believe, will ensure that providers only work with legitimate third parties that have adopted KYUP practices that meet the baseline standards we establish.
                    </P>
                    <P>
                        <E T="03">Compliance and recordkeeping responsibilities.</E>
                         We believe that for voice service providers to fulfill their KYUP obligations, they will need to have adequate policies and procedures in place, and we seek comment on whether we should require providers to establish any specific policies and procedures. We note that the I3Forum Know Your Customer/Know Your Traffic Code of Conduct suggests that providers should “identify at least one person who will have particular responsibility for upholding the policy” and it suggests and describes the duties of that compliance leader. The duties of the KYC compliance leader and their team include: “[p]erforming pre-agreement reviews of all prospective customers to determine whether they meet the corporate KYC and KYT policy requirements, keeping documentation of all information considered, decisions reached, and all the individuals involved in the review[;] [p]erforming escalated enhanced due diligence reviews and making KYC decisions for higher-risk clients identified through the standard review process[;] [e]nsuring corporate policy is sufficient to meet changes in legal and regulatory obligations and consulting with internal teams on legal questions that arise as part of KYC processes[;] [s]upporting the development or implementation of the tools, systems, or other resources needed to perform and document KYC and KYT in a timely manner[; and] [w]orking with line management and human resources management to ensure the adequacy of the KYC and KYT training that is given to staff.” Should we adopt such a requirement for the KYUP obligations? Should we require that providers implement close coordination between sales teams and compliance teams to ensure that the KYUP steps occur before a provider agrees to provide service to an upstream provider?
                    </P>
                    <P>
                        We propose that voice service providers retain the KYUP information they collect for each upstream provider for the entirety of any potential statute of limitations relating to the use of its network or services to transmit illegal calls—
                        <E T="03">i.e.,</E>
                         for a minimum of four years. 
                        <PRTPAGE P="42609"/>
                        We seek comment on this proposal. Should we consider a longer or shorter retention timeframe? What are the industry standard retention periods for business customer information? Would such information retention implicate the security of sensitive business or personal information, and if so, what safeguards can we implement to address this? In the event we allow providers to use third parties to complete their KYUP obligations, we believe the provider should maintain the obligation to supply the information in the event of an investigation under our proposals, and would therefore need to ensure it can obtain the information from the third party in a timely manner upon request.
                    </P>
                    <P>We also seek comment on whether voice service providers should undergo any compliance reviews related to their KYUP obligations. For instance, should we require providers to obtain independent verification of their compliance, such as through an independent auditor using generally accepted auditing practices? How often should such reviews be conducted? Should they be randomized? Should reviews generally evaluate all provider KYUP practices or be targeted toward specific practices, such as those where there appear to be the greatest weaknesses by providers at the time? What role, if any, should the Commission play in such compliance reviews? Should we require providers to report the findings of such reviews to the Commission?</P>
                    <P>
                        <E T="03">Implementation costs and cost recovery.</E>
                         We seek comment on the costs of the KYUP obligations for voice service providers. As an initial matter, we believe that many legitimate providers already perform many of the baseline KYUP steps we propose above to fulfill their existing obligation to know their upstream providers, and therefore their costs will be minimal. We believe the greatest cost would be incurred by providers that have not implemented the most basic KYUP practices to comply with that existing obligation, and we believe that cost would be warranted. We seek comment on what share of providers would need to adopt new processes and what share would only need to make minor adjustments. What costs would providers who only require minor changes to their current procedures incur? We believe that providers that seek to enter into business with a number of upstream providers will also incur greater costs but that those costs are warranted as they will ensure that wholesale providers are employing proper measures to deter bad actor providers. Upstream providers that only have a direct relationship with end users will not incur these costs. We also believe our proposed baseline KYUP requirements minimize the costs incurred by obligated providers by enabling them to rely on upstream providers to supply most of the information they must obtain and only prescribing basic due diligence. Additionally, we believe that responsible providers already collect most of this information as part of their normal onboarding process with new upstream providers. We seek comment on this assessment and on the specific costs providers, including small providers, may face for each of the requirements we propose above.
                    </P>
                    <P>We also think that the costs associated with being subject to a downstream provider's KYUP obligations will be reasonable for legitimate and responsible upstream providers. Nearly all voice service providers may bear some costs in compiling the requested KYUP information and providing it to downstream providers, but we believe many upstream providers will have this information readily available. Upstream providers will also be able to share the same information with all downstream providers with which they do business. In any event, the fact that they will have to provide information will, we believe, spur all voice service providers in the ecosystem to be more responsible actors, ensuring that they have completed necessary registrations and can provide information showing they are a legitimate business. We seek comment on these views.</P>
                    <P>We seek comment on whether we should put guardrails on how voice service providers will recover these costs. Will providers treat this as a cost of doing business and recover such costs from their customers? Will they attempt to charge upstream providers for the costs of performing their KYUP obligations? Should we explicitly permit or prohibit any specific cost recovery approaches?</P>
                    <P>
                        <E T="03">Safe harbor for accepting calls from upstream providers who obtain SPC tokens.</E>
                         Below we propose to require that the Governance Authority strengthen its SPC token access policy, including certain steps to know voice service providers that are modeled on the KYUP requirements above, and increase its enforcement of the policy. In the event we adopt those requirements, we seek comment on whether we should create a safe harbor from Commission enforcement of KYUP requirements if a provider provides service to an upstream provider that has and maintains an SPC token with specific regard to the KYUP requirements that would duplicate the token access policy requirements. We believe such a safe harbor could reduce providers' costs of performing KYUP requirements. However, we are concerned it could undermine the ability of providers to perform KYUP monitoring obligations because they would not have obtained certain information about upstream providers to compare against. Should we require the Governance Authority to share information with providers that they can use to support their monitoring activities? Should this safe harbor only apply to small providers?
                    </P>
                    <P>
                        <E T="03">Best practices.</E>
                         We seek comment on whether, instead of requiring voice service providers to follow the specific baseline KYUP obligations we propose above, we should establish those proposed requirements as best practices or advise providers to use existing resources as best practices. Should we delegate authority to the Wireline Competition Bureau (Bureau) to establish and maintain best practices, as needed, in coordination with the Consumer and Governmental Affairs Bureau and the Enforcement Bureau? Are there specific existing best practices resources we should advise providers to use? Should we establish a safe harbor from Commission enforcement of the general KYUP requirement for providers that do adopt the best practices? How would such a safe harbor work? Alternatively, should we adopt a rule requiring providers to use a specific best practices resource?
                    </P>
                    <P>
                        <E T="03">Liability standard for Commission enforcement.</E>
                         We seek comment on whether we should establish a liability standard the Commission could use to hold voice service providers accountable for complying with their KYUP obligations. We remain concerned that certain providers may seek to circumvent these obligations. Should we establish that the Commission can hold a provider accountable if it knew or should have known that an upstream provider is using its network or services to transmit illegal calls? Should we establish a different liability standard? If so, what liability standard would best spur providers to take their KYUP obligations seriously without placing an unreasonable threat of enforcement on those providers that make legitimate efforts to fulfill those obligations? Should we establish a liability standard as an alternative to establishing the baseline KYUP obligations we propose? Should we establish a liability standard for providers who abuse their KYUP obligations, such as using them to 
                        <PRTPAGE P="42610"/>
                        advance anticompetitive goals? If so, should the standard be whether a decision to refuse or discontinue service was objectively reasonable?
                    </P>
                    <HD SOURCE="HD3">2. Enhancing Oversight of Voice Service Providers by the STIR/SHAKEN Governance Authority</HD>
                    <P>The STIR/SHAKEN framework is predicated on trust. The STIR/SHAKEN Governance Authority establishes and enforces the policies and procedures that determine which voice service providers can participate in the STIR/SHAKEN ecosystem so that authentication information is applied by trusted entities. When we refer to the Governance Authority, we include the Policy Administrator and the Certification Authorities even though each entity may perform specific functions, unless otherwise specified. The technical requirements establish a secure mechanism to transmit authentication information so that it remains trustworthy. As originally contemplated, this framework would allow for originating providers to develop a reputation based on the calls they sign and for terminating providers to treat calls differently based on that reputation, which might deter originating providers from transmitting illegal calls. However, trust in the STIR/SHAKEN framework can break down when there are bad actor providers in the ecosystem that are not implementing the framework consistently or correctly, including originating providers that fail to authenticate calls or do not apply the proper attestations, downstream providers that accept those calls, and terminating providers that fail to verify authentication information.</P>
                    <P>We do not believe that the Governance Authority's current policies and practices are sufficiently preventing bad actor providers from entering the STIR/SHAKEN ecosystem. Because this can undermine the trust on which STIR/SHAKEN is built, we propose and seek comment on steps we should take to enhance the Governance Authority's role in serving as a gatekeeper to the ecosystem. Specifically, we propose to require that the Governance Authority adopt improved policies that include affirmative, effective measures to prevent voice service providers that are issued SPC tokens from transmitting calls that are not in compliance with the STIR/SHAKEN authentication framework, the Commission's STIR/SHAKEN rules, or the Governance Authority's policies and to prevent Certification Authorities from failing to comply with the STIR/SHAKEN authentication framework, the Commission's STIR/SHAKEN rules, or the Governance Authority's policies. We propose that such policies include enhancements for the issuance and revocation of SPC tokens and the selection and removal of Certification Authorities, including taking greater action to enforce those policies. We also propose that the Governance Authority apply those policies to existing SPC token holders and Certification Authorities within six (6) months after any rules we adopt go into effect. We believe these enhancements will not only help restore trust in the STIR/SHAKEN framework, but will help keep bad actor providers off the voice network, particularly if we adopt our proposal to prohibit voice service providers from accepting unauthenticated SIP calls.</P>
                    <P>In advancing these proposals, we acknowledge that we would be applying a more directed oversight approach with the Governance Authority, but we believe Commission intervention now is necessary to restore trust in the STIR/SHAKEN framework, and that we have authority to do so. Although the Commission found that intervention in the independent STIR/SHAKEN governance structure was not appropriate when it first mandated that voice service providers implement STIR/SHAKEN given that the Commission “[did] not know the nature and scope of the problems that may arise,” it has consistently contemplated—since before the Governance Authority was established—that it could play a greater oversight role if necessary. With greater experience, we now believe that we have identified problems that the Commission can address by requiring updated policies and requirements. We seek comment on these views.</P>
                    <P>
                        <E T="03">Policies for the issuance of SPC tokens and selection of Certification Authorities.</E>
                         We propose to direct the Governance Authority to revise its SPC token access policy to include baseline vetting requirements prior to the issuance of SPC tokens that are modeled off the KYUP requirements we propose above, and that these requirements should also be applied to existing SPC token holders. We do not believe that the Governance Authority's current SPC token access policy is sufficient to prevent bad actor providers from obtaining a token, which in turn authorizes them to access the certificates needed to authenticate calls, and then use those certificates to sign calls that are not in compliance with the STIR/SHAKEN authentication framework and the Commission's STIR/SHAKEN rules. Under the existing SPC token access policy, providers must: (1) have a current form 499-A on file with the Commission, (2) have been assigned an Operating Company Number (OCN), and (3) have certified with the Commission that they have implemented STIR/SHAKEN or comply with the Commission's robocall mitigation program requirements and are listed in the RMD. Although the existing policy subjects voice service providers seeking SPC tokens to some level of scrutiny, it does not include an evaluation of whether a provider is a legitimate entity or provide the gatekeeping necessary to keep potential bad actor providers out of the STIR/SHAKEN ecosystem. Accordingly, we propose to require the Governance Authority to modify its policy to include all of the KYUP information collection, compliance review, and verification requirements we propose above. We also propose to require that the Governance Authority adopt a policy to review this information and deny an SPC token when there is a reasonable basis for believing the SPC token holder is unlikely to comply with the STIR/SHAKEN authentication framework, the Commission's STIR/SHAKEN rules, and/or the Governance Authority's policies. We seek comment on our proposals and associated analysis. Are there any such KYUP requirements we should not require the Governance Authority to follow? How do these relate to the information collection requirements of, and due diligence performed by, the National Exchange Carrier Association (NECA) when providers request OCNs? Should we require other changes to the Governance Authority's SPC token access policy to deter bad actors?
                    </P>
                    <P>
                        We likewise propose to require the Governance Authority to follow certain KYUP requirements to vet entities seeking to become Certification Authorities prior to their selection, and that these requirements should be applied to existing Certification Authorities. The Governance Authority has not published a written policy governing the selection of Certification Authorities. Rather, the Governance Authority has established a policy for governing the issuance of certificates that is consistent with the STIR/SHAKEN standards, which Certification Authorities must follow in order to be considered a “trusted” Certification Authority. We are concerned that some Certification Authorities may not be following the certificate issuance policy or otherwise may be enabling illegal calls. While a robust Certification Authority removal process could address such concerns, we believe the 
                        <PRTPAGE P="42611"/>
                        Governance Authority should take steps to identify bad actors before they are selected as Certification Authorities. Accordingly, we propose to require the Governance Authority to establish a policy for the selection of Certification Authorities and that such policy should include following all of the KYUP information collection and information verification requirements we propose above. We also propose to require that the Governance Authority policy include reviewing this information and denying selection of an entity as a Certification Authority when there is a reasonable basis for believing the entity is unlikely to comply with the STIR/SHAKEN authentication framework, the Commission's STIR/SHAKEN rules, and/or the Governance Authority's policies. We seek comment on our proposals and associated analysis, including whether we should require greater or lesser due diligence obligations. Should we also require the Governance Authority to adjust the certificate issuance policy, such as by reducing the maximum permissible expiration timeline for a certificate?
                    </P>
                    <P>We also seek comment on whether we should require the Governance Authority to establish a conflict of interest policy governing Certification Authorities' relationships with voice service providers, including when they are also acting as voice service providers, and what that policy should entail. Although the Governance Authority has established a policy concerning conflicts as to a Certification Authority also serving as the Policy Administrator, it has not established a conflict-of-interest policy as to a Certification Authority also acting as a provider or having common ownership with providers for which the Certification Authority issues certificates. We are concerned about such relationships because a Certification Authority may have incentive to issue certificates to providers to which they are related without following the certificate issuance policy or in a way that otherwise enables illegal calls. We seek comment on this assessment. Should we also require the Governance Authority to revise its certificate issuance policy so that Certification Authorities have a responsibility to not issue certificates to entities that are likely to use certificates to sign illegal calls?</P>
                    <P>
                        <E T="03">Policies for the revocation of SPC tokens and removal of Certification Authorities.</E>
                         We propose to require that the Governance Authority play an active role in obtaining information about providers misusing their SPC tokens and take appropriate action on any information it receives or obtains. Under the Governance Authority's existing SPC Token revocation policy, providers must sign an agreement that contains the terms for which tokens may be used, such as in compliance with the STIR/SHAKEN standards governing proper attestations. The policy further states that the Governance Authority may revoke SPC tokens upon indication that a provider is in breach of the agreement, and lays out other specified reasons for revocation. Additionally, the policy imposes a standardized process stakeholders must use to report potential SPC token misuse. The stakeholders identified by the policy include the Policy Administrator, Certification Authorities, voice service providers, members of the Governance Authority board, Alliance for Telecommunications Industry Solutions (ATIS) staff, regulatory authorities (
                        <E T="03">e.g.,</E>
                         the FCC and FTC), consumers, and third parties. Despite well-known reports that providers are applying improper attestations to calls or otherwise failing to follow the STIR/SHAKEN standards, the Governance Authority has reported to Commission staff that it has not permanently revoked SPC tokens of its own accord except for providers that have failed to pay required fees or failed to supply annual FCC Form 499 revenue data, which the Governance Authority uses to calculate fees. The Governance Authority has revoked SPC tokens in response to Commission enforcement actions against certain providers, and it reports that it has engaged with some providers who were subject to complaints about improper attestations, but that the providers cured their violations prior to SPC token revocation or after revocation, resulting in reinstatement. We believe the Governance Authority may be hindered in enforcing the SPC token policy by relying on an overly formal reporting process to obtain information and that it may be too forgiving in enforcing the policy. To address these issues, we first propose to require that the Governance Authority establish formal information sharing arrangements with the Industry Traceback Group and call analytics providers to receive information about specific providers' practices. We also propose to require the Governance Authority to review and evaluate information it receives from any sources, even in the absence of formal reports. We further propose to require that the Governance Authority enhance its procedures for acting on suspected violations, and we seek comment on how its procedures should be enhanced so providers that violate the STIR/SHAKEN authentication framework, the Commission's STIR/SHAKEN rules, and/or the Governance Authority's policies are permanently removed from the STIR/SHAKEN ecosystem. We seek comment on our proposals and any aspects of our analysis. Should we require the Governance Authority to seek additional information about providers? Should we require it to relax its reporting policy so that stakeholders can submit information informally or anonymously?
                    </P>
                    <P>
                        We propose to require that the Governance Authority also play a more active role in seeking information, and taking action on information it receives, about Certification Authorities failing to follow the STIR/SHAKEN authentication framework, the Commission's STIR/SHAKEN rules, and/or the Governance Authority's policies. As noted, the Governance Authority has established a policy governing the issuance of certificates by Certification Authorities. It has also established a policy for the suspension or removal of Certification Authorities that violate the policy, violate their agreement with the Governance Authority, or have been involved in a cybersecurity incident. Commission staff is concerned about anecdotal evidence that certain Certification Authorities issue a disproportionate number of certificates that are being used by voice service providers applying improper attestations to their calls, and we seek record evidence demonstrating this concern. We believe this indicates that the Governance Authority policies do not sufficiently guard against misuse of certificates and the role Certification Authorities may play in such misuse. To our knowledge, the Governance Authority has not suspended or removed any Certification Authorities. Commission staff has observed changes in the number of Certification Authorities, but believes those have been due to voluntary decisions by Certification Authorities. We propose to require that the Governance Authority establish a process to accept information about Certification Authority practices from stakeholders, including a process to regularly obtain information from call analytics providers. We further propose to require that the Governance Authority initiate investigations into Certification Authorities with suspect practices, such as granting certificates to providers responsible for a high volume of illegal calls associated, and remove Certification Authorities who are found to be violating the STIR/SHAKEN authentication framework, the 
                        <PRTPAGE P="42612"/>
                        Commission's STIR/SHAKEN rules, and/or the Governance Authority's policies. We seek comment on whether we should require the Governance Authority to obtain other information about Certification Authority practices that would inform their oversight. We further seek comment on whether we should require the Governance Authority to update its policies to better address the misuse of certificates and the role that Certification Authorities may play in such misuse, and if so, how. We also seek comment whether the Governance Authority has established adequate steps providers must take when they were issued certificates from a Certification Authority that was subsequently removed.
                    </P>
                    <P>We seek comment on whether we should require that the Governance Authority review and act on any information it receives or obtains about voice service providers or Certification Authorities within a specific time. We note that bad actor providers can transmit a significant number of non-compliant calls in a short period of time. Is 10 business days a sufficient time period in which the Governance Authority can reasonably review evidence of wrongdoing and take action? Should it be longer or shorter? Should we require the Governance Authority to adopt a policy to immediately suspend an SPC token or Certification Authority when presented with evidence of egregious activity, after which it can conduct a more thorough review and final determination?</P>
                    <P>
                        <E T="03">Implementation barriers.</E>
                         We seek comment on any barriers to the Governance Authority following any of the requirements we proposed above. Are there steps the Commission or the Governance Authority can take to facilitate information sharing? Are there specific reasons the Governance Authority may be deterred from obtaining information or enforcing the policies, such as resource or liability concerns? Can any costs associated with obtaining any such information be incorporated into other Governance Authority operational expenses that are paid for by fees from providers obtaining SPC tokens? Is there a safe harbor we can grant to the Governance Authority for denials and revocations that would support it taking action, and if so, how would the safe harbor be applied? Should we permit the Governance Authority to use third parties to perform some or all of the required vetting?
                    </P>
                    <P>
                        <E T="03">Appeals.</E>
                         We propose to allow parties to appeal Governance Authority decisions to the Commission. The Commission has already established a process for voice service providers to appeal token revocation decisions to the Commission. Should we establish a similar process for entities removed as Certification Authorities, as well as for when providers are denied SPC tokens and entities denied as Certification Authorities in the first instance? How, if at all, should the appeals process be different? Should aggrieved entities be required to appeal to the Governance Authority before it would be allowed to file such appeals with the Commission? Should we also allow stakeholders to appeal decisions by the Governance Authority declining to revoke an SPC token, remove a Certification Authority, or initiate an investigation? How might this appeal process work or might there be a better process for entities to alert the Commission to the Governance Authority's decisions they perceive to be erroneous? Should we require the Governance Authority to respond to stakeholders that submit complaints if it declines to take any of those actions?
                    </P>
                    <P>
                        <E T="03">Reporting.</E>
                         We propose to require that the Governance Authority report to the Commission on a quarterly basis information about its enforcement activity, including complaints it has received, investigations it has initiated or concluded, and decisions concerning SPC token revocations and Certification Authority removals, including any reports documenting the Governance Authority's final determinations. We believe that such reporting will aid the Commission in its efforts to identify and take action against bad actor providers. We seek comment on this proposal.
                    </P>
                    <HD SOURCE="HD2">B. Raising STIR/SHAKEN Attestation Standards</HD>
                    <P>An attestation is a voice service provider's assertion about the knowledge it has of its customer and the customer's right to use a telephone number. A provider may assert A-level (or “full”) attestation when it (1) is responsible for the origination of the call onto the IP network, (2) has a direct authenticated relationship with its customer and can identify the customer, and (3) has established a verified association between its customer and the telephone number used for the call. It may assert B-level (or “partial”) attestation when it can satisfy elements (1) and (2), but not (3). It must assert C-level (or “gateway”) attestation when the provider has no relationship with the originator of a call, such as when a provider is acting as an international gateway. The ATIS standards also permit a C-level attestation when a provider is unable to satisfy the criteria of A- or B-level attestations. By asserting full (A-level) attestation, the provider is claiming that is has knowledge that the number has not been spoofed. While calls receiving partial (B-level) or gateway (C-level) attestations are not necessarily spoofed, they indicate that the voice service provider lacks sufficient knowledge to conclusively determine that fact.</P>
                    <P>
                        Many calls are being authenticated by originating providers with improper attestations, according to a 2024 report from the STIR/SHAKEN Governance Authority. The 
                        <E T="03">Call Branding FNPRM</E>
                         record is replete with comments making the same case. The Commission has acknowledged the problem too, and has taken some steps to address it. The 
                        <E T="03">Lingo Order</E>
                         represents the most high-profile example, in which the Commission found that Lingo Telecom applied A-level attestations to 3,978 spoofed robocalls carrying a deepfake generative AI voice message purporting to be from then-President Joe Biden. Recent data show that “93.4% of robocall traffic from the most prolific robocall signers now carry A-level attestations” and “48 percent of illegal calls are A-attested.” In an analysis done by the American Bankers Association “of 12,900 calls that illegally spoofed telephone numbers belonging to 47 large banks, retailers, and healthcare providers, more than half of the calls received an A-level or B-level attestation.” Improper signing practices are not limited to bad actor providers. Transaction Network Services reports that, based on internal data covering the first half of 2025, “certain top tier carriers had marked around 8% of their invalid number calls with A-level attestation, and non-top tier carriers had marked 57% of their invalid number calls with A-level attestation.”
                    </P>
                    <P>
                        These findings call for enhancements to the Commission's STIR/SHAKEN implementation rules. Improper attestations undermine the trust in and integrity of the STIR/SHAKEN framework, and its value in supporting efforts to combat illegal robocalls. When attestations are improper, terminating providers do not have trustworthy information concerning whether the number used for the call was illegally spoofed. Because voice service providers also use attestations to inform call analytics engines, improper attestations can undermine their effectiveness, contributing to inaccurate blocking and labeling determinations. And because the Commission has proposed in the 
                        <E T="03">Call Branding FNPRM</E>
                         to prohibit terminating providers from delivering indications of A-level attestations to consumers' devices 
                        <PRTPAGE P="42613"/>
                        unless they also deliver verified caller identity information, improper attestations may subvert the validity of caller identity information rather than serve to enhance it. Ultimately, improper attestations may lend false legitimacy to bad actors and may undermine the credibility of good actors.
                    </P>
                    <P>Given these stated harms, stakeholders have called on the Commission to take a stronger role in overseeing and enforcing voice service providers' compliance with the ATIS attestation standards. We believe the primary cause for improper attestations is a lack of specificity on what practices are permissible for satisfying each of the attestation-level criteria. We also believe improper attestations result from disagreement about what mechanisms are permitted to close the attestation “knowledge gap.” As we understand it, this knowledge gap generally occurs in the following general scenarios:</P>
                    <P>
                        <E T="03">Scenario 1</E>
                        —When the originating provider that is authenticating the call is a separate entity from the telephone number service provider (TNSP) that provisioned the telephone numbers to the customer initiating the call, such as when a TNSP assigns direct inward dialing (DID) numbers to a customer that initiates the call with another voice service provider.
                    </P>
                    <P>
                        <E T="03">Scenario 2</E>
                        —When the originating provider does not have a direct relationship with the end user because the end user obtained voice service from an intermediary provider, such as a reseller that may be several steps removed from the originating provider if the service is resold multiple times. This scenario is a direct result of the STIR/SHAKEN implementation exemption for non-facilities-based providers that is inherent in the STIR/SHAKEN framework and which we propose to codify below. We also propose to close this knowledge gap by requiring all voice service providers serving end users directly to make attestation-level decisions regarding those end users' calls.
                    </P>
                    <P>
                        We do not believe these scenarios are mutually exclusive, and therefore both could exist with respect to a single call. We seek comment on this assessment. Are there other scenarios that cause a knowledge gap? We believe that bad actors may take advantage of the “knowledge gap” to obscure their identity to the originating provider and use that obscurity to generate spoofed or unlawful calls. As we raised in the 
                        <E T="03">Call Branding FNPRM,</E>
                         the knowledge gap can also undermine the ability for providers to verify caller identity verification information. We seek comment on these views. As a technical matter, we believe there is also a knowledge gap when a gateway provider is authenticating a call that it received from a foreign voice service provider and when an intermediate provider is authenticating an unauthenticated call it receives, but these circumstances are outside the scope of the problem we seek to address here.
                    </P>
                    <P>
                        We propose specific requirements and guardrails to govern STIR/SHAKEN attestation-level decisions to ensure that voice service providers base such decisions on sufficient knowledge about their customer and the customer's right to use a number, and not on factors that may be unrelated to caller ID information. Although we believe the main driver of improper attestations is the presence of bad actor providers in the ecosystem, which we believe will be addressed by the KYUP and Governance Authority proposals above, we also want to ensure that all providers in the ecosystem are applying attestations consistently and correctly. We also seek to provide a clearer foundation for enforcement when providers misapply attestations. Accordingly, we propose to: (1) codify the attestation levels established in the ATIS standards and the criteria that apply to them, (2) set out requirements to satisfy the attestation-level criteria including closing the attestation knowledge gap in Scenario 1, and (3) codify the definition for and prohibitions on improper attestations that are implicit in providers' obligation to implement the STIR/SHAKEN standards. We believe the proposals will serve to enhance the STIR/SHAKEN standards and better achieve the intended outcomes of the TRACED Act without superseding the requirement that providers implement the STIR/SHAKEN standards, as required by the TRACED Act. We seek comment on this analysis, including the extent to which our proposals will address all causes of improper attestations and our authority to take these actions. We also seek comment on whether we should require providers to implement the most current version of the STIR/SHAKEN standards, rather than the version that was in effect at the time they were first required to implement STIR/SHAKEN. In the 
                        <E T="03">First Caller ID Authentication Report Order,</E>
                         85 FR 22029 (April 21, 2020) and in subsequent orders, the Commission required providers to comply with the versions of those standards that were in effect at the time of their respective compliance deadlines, including any errata as of those dates or earlier. The Commission delegated to the Bureau authority: (1) to determine whether to seek comment on requiring compliance with revised versions of the three ATIS standards associated with the STIR/SHAKEN authentication framework, and all documents referenced therein; (2) to require providers subject to a STIR/SHAKEN authentication requirement to comply with those revised standards; and (3) to set appropriate compliance deadlines regarding such revised standards. In doing so, the Commission noted that providers will only be required to implement new standards if the benefits to the STIR/SHAKEN ecosystem outweigh any compliance burdens. Notwithstanding our delegation of authority to the Bureau, we seek to address the question here.
                    </P>
                    <HD SOURCE="HD3">1. Codifying the Attestation Levels</HD>
                    <P>
                        We propose to codify the three attestation levels—A, B, and C—and the criteria that apply to each level. We believe that this step goes hand-in-hand with establishing steps voice service providers must take to satisfy the attestation-level criteria, as we propose to do below. We also think it will clarify any perceived ambiguity about the attestation levels by providers and provide a stronger foundation for oversight and enforcement of attestation-level decisions. We seek comment on this proposal. In particular, are there meaningful concerns with codifying the attestation levels when the Commission has acknowledged that ATIS standards may change over time? Are ATIS and/or the Governance Authority continuing to study the problem of improper attestations and planning to issue more particularized guidance? Is ATIS in the process of changing the attestation levels or their criteria, particularly in light of the issues with improper attestations? We note ATIS's view in the context of non-IP caller ID authentication standards that “[s]tandards are not a proxy for regulations” and that “standards should not be used as the primary basis for regulation without significant independent legal and factual analysis to evaluate whether the standard is viable or appropriate for a regulatory mandate to implement solution(s) based on that standard.” Given the widespread support for and investment in STIR/SHAKEN, we believe that the attestation portion of the standard is viable and appropriate for codification. We seek comment on these views and any other legal or factual analysis that we should consider in our assessment.
                        <PRTPAGE P="42614"/>
                    </P>
                    <HD SOURCE="HD3">2. Requirements To Satisfy the Attestation Level Criteria</HD>
                    <P>We propose and seek comment on specifying how voice service providers may satisfy the criteria used for applying the STIR/SHAKEN attestation levels to dispel any perceived ambiguity about how the criteria apply and ensure providers are making proper attestation decisions. We believe doing so is necessary, given the evidence of improper attestations by providers of all types and stakeholders' requests that the Commission provide greater oversight of attestation practices. We seek comment on this proposal. Do commenters agree it is necessary to specify how attestation-level criteria are satisfied to address improper attestations? Are providers using the absence of such specificity to skirt their attestation responsibilities? Are there other reasons, beyond differences in interpretation or implementation of the ATIS standards, as to why many providers are improperly attesting to calls? Rather than adopting requirements, should we establish best practices, and should we delegate authority to establish those best practices to the Bureau? If we do establish requirements for satisfying attestation-level decisions, would this instill enough trust in attestations that we should prohibit blocking or spam labeling of calls with A-level attestations? What about B-level attestations? What incentives would that provide to originating providers?</P>
                    <P>
                        <E T="03">Responsibility for call origination.</E>
                         We propose that for a voice service provider to satisfy the requirement that it is responsible for the origination of the call onto the IP network, it must qualify for the definition of “origination” that we propose to adopt below. We seek comment on this proposal. If we adopt our proposal to define “origination” as the technological act of placing a customer's outgoing call onto the network using the provider's own facilities, does this offer enough clarity about which provider is responsible for originating a call onto the IP network? If not, how can we provide greater clarity? We believe that, under our definition of “origination,” neither intermediate providers, including gateway providers, nor initiating providers, as we propose to define that term below, can be responsible for the origination of a call. In our discussion surrounding our proposals to define “origination” and “originating provider” and “facilities-based provider” and “non-facilities-based provider,” we seek comment on whether under our proposed definition of “origination,” only facilities-based providers can be originating providers, meaning non-facilities-based providers cannot be responsible for the origination of a call. Is this understanding correct?
                    </P>
                    <P>
                        <E T="03">Direct authenticated relationship with the customer and ability to identify the customer.</E>
                         We propose that for an originating provider to satisfy the requirement that it have a direct, authenticated relationship with the customer associated with the call and be able to identify the customer, it must satisfy any KYC or KYUP requirements established by the Commission. We seek comment on this proposal. The KYC requirement would apply when the originating provider is authenticating a call for an end user customer. Section 64.1200(n)(4) of the Commission's rules establishes the current KYC requirement, and in the 
                        <E T="03">KYC FNPRM,</E>
                         the Commission seeks comment on specific requirements originating providers must follow to fulfill this requirement. The KYUP requirement would apply when the originating provider is authenticating a call from a customer that is a direct upstream provider, such as when the originating provider's customer is a reseller. As discussed above, Section 64.1200(n)(5) of the Commission's rules establishes a KYUP requirement, and all voice service providers must describe their KYUP practices in the robocall mitigation plans they file in the RMD. We also propose above to establish specific requirements providers must follow to fulfill the KYUP requirement. We believe that tying KYC and KYUP requirements to attestation-level decisions will help ensure originating providers actually know their customer before assigning A- or B-level attestations to calls, making such attestations more accurate and thereby better deterring impermissible spoofing. Do commenters agree? Are there other benefits? Are there any drawbacks? Should we only require originating providers to rely on specific KYC or KYUP practices to fulfill this criterion? If so, which practices? We also seek comment on how this proposal relates to the 
                        <E T="03">Call Branding FNPRM,</E>
                         which seeks comment on requiring originating providers to verify customer identity information as a condition of A-level attestation.
                    </P>
                    <P>
                        <E T="03">Establishing a verified association between the customer and the telephone number used for the call.</E>
                         We propose to specify permissible and impermissible mechanisms an originating provider may use to establish a verified association between its customer and the telephone number used for a call. We do not believe all originating providers are meaningfully verifying a customer's association with a telephone number, leading to improper attestations. This stems, we believe, from ATIS-1000074, which states that “[u]ltimately it is up to service provider policy to decide what constitutes [a] `legitimate right to assert a [telephone number]' but the service provider's reputation may be directly dependent on how rigorous they have been in making this assertion.” We believe that some originating providers are interpreting this direction too broadly.
                    </P>
                    <P>
                        To resolve these practices, we propose two mechanisms that providers may use to establish a customer's association with a number. First, we propose to find that an originating provider may establish a verified association between its customer and the telephone number used when the originating provider is the TNSP (
                        <E T="03">i.e.,</E>
                         it assigned the telephone number to the customer either as an individual number or as part of a range of numbers). Second, we propose to partially close the knowledge gap in Scenario 1 by finding that delegate certificates are a viable method for originating providers to establish a verified association between a customer that is an initiating provider and the number being used to initiate the call, and we seek comment on this view. Delegate certificates, which are described in ATIS-1000092 (a separate ATIS standard than those required for STIR/SHAKEN implementation), allow an entity to obtain a certificate from the TNSP that demonstrates the entity's authority to use the number and present that certificate to the originating provider. We believe this process would enable initiating providers to satisfy this criterion whenever its end user customer uses a telephone number that the initiating provider assigned to the end user. To what extent are providers already using delegate certificates for this purpose? What measures, if any, are needed to ensure that delegate certificates are accepted as a valid form of showing an initiating provider has a relationship with a number? Must we require that originating providers accept delegate certificates from initiating providers as evidence they have a verified association with a number, and if so, should we place any guardrails on this requirement? In the 
                        <E T="03">Eighth Caller ID Authentication Order,</E>
                         90 FR 40241 (Aug. 19, 2025)), the Commission declined to mandate acceptance of delegate certificates, concluding that such a mandate was beyond the scope of the third-party authentication rules adopted in that 
                        <E T="03">Order</E>
                         and that the record in that proceeding was 
                        <PRTPAGE P="42615"/>
                        insufficient to weigh the benefits and burdens of imposing such a requirement. Given our aim to close the knowledge gap, we seek to develop a more robust record on the issue. What are the benefits and drawbacks of the delegate certificate approach? Because the delegate certificate would be associated with the TNSP, would it enable the TNSP to be held accountable for the illegal calls transmitted by entities to which they assigned numbers? We also seek comment on whether we should make a determination as to whether delegate certificates are a permissible method for originating providers to establish a verified association between an end user customer, such as a non-voice service provider enterprise, and the number being used to initiate the call. ATIS-1000092 contemplates that end users that are non-provider enterprises could also obtain delegate certificates from a TNSP and present them to voice service providers to establish their association with the telephone number they are using. To what extent are delegate certificates already being used for this purpose? What are the risks and benefits of allowing non-provider entities to participate in the STIR/SHAKEN ecosystem in this fashion? We seek comment on any additional provider and customer arrangements for which delegate certificates could be used to establish a customer's association with a number.
                    </P>
                    <P>Conversely, we believe there are two mechanisms a voice service provider cannot use to establish a verified association between its customer and the telephone number used. First, we do not believe this association can be established by a business agreement or certification that includes only a general statement that the customer will only use numbers with which it has a verified association. This is essentially the mechanism that Lingo Telecom used when it misassigned A-level attestations for spoofed calls. Second, we do not believe an association can be established when a number qualifies as a Do-Not-Originate (DNO) number by default. We seek comment on these beliefs.</P>
                    <P>
                        We seek comment on whether we should specify other mechanisms an originating provider can use to establish a customer's association with a telephone number. Should we require that providers obtain reasonable evidence of a customer's association with a number? Should we allow business agreements or certifications that specify the active telephone numbers the customer will use? In the 
                        <E T="03">Robocall Numbering Policies NPRM</E>
                         (91 FR 25312), we sought comment on “better means of tracking the chain of custody of numbering resources,” such a numbering database, and we seek comment on whether any such solution we establish could be used by providers to verify customer associations with telephone numbers. Do commenters believe the still-in-development VESPER standard, which is described as an extension of delegate certificates that establishes an entity or individual's verified right-to-use a number after the entity is vetted, could be used for this purpose?
                    </P>
                    <HD SOURCE="HD3">3. Attestation Prohibitions</HD>
                    <P>We propose to define improper attestation and establish an affirmative prohibition on voice service providers engaging in improper attestation practices, including willfully assigning improper attestations and using other criteria to make attestation-level decisions. Although we believe the existing requirement that providers implement STIR/SHAKEN using the STIR/SHAKEN standards necessarily requires that they apply attestations based on the criteria described above, we believe that codifying these prohibitions will establish a clear floor and ceiling for each attestation level and a firmer foundation for enforcement of improper attestations. We seek comment on these views.</P>
                    <P>
                        <E T="03">Defining “improper attestation.”</E>
                         We propose to define improper attestation as any attestation level that does not conform to ATIS-1000074 and the Commission's rules, including any attestation that is inconsistent with the information the voice service provider has, or is required to have, about the call. This proposed definition largely mirrors the definition established by the Governance Authority in guidance concerning improper authentication and attestations, and we believe it properly captures what constitutes an improper attestation. We seek comment on this proposal. We do not, at this time, propose to establish requirements related to improper authentication, but we note that the guidance defined improper authentication as the use of a certificate “to authenticate any information contained within an STI-GA recognized SHAKEN extension that is known to be false, or information that is outside the scope of the U.S. STIR/SHAKEN framework.”
                    </P>
                    <P>
                        <E T="03">Prohibiting voice service providers from willfully making improper attestations.</E>
                         We propose to prohibit voice service providers from willfully assigning attestations that are higher or lower than permissible under the STIR/SHAKEN standards and any rules we establish. ZipDX provides evidence that voice service providers may improperly apply higher-than-permissible attestations if they want their calls to be viewed as more trustworthy and lower-than-permissible attestations if they want their calls to be transmitted with less scrutiny. Is there other evidence that providers are or have the incentive to willfully apply improper attestations? Should we find that specific practices constitute improper attestation, such as a C-level attestation by a provider that originates a call or an A- or B-level attestation when the provider authenticating the call is a gateway provider or non-gateway intermediate provider?
                    </P>
                    <P>
                        <E T="03">Prohibiting providers from using other criteria in making attestation-level decisions.</E>
                         We propose to prohibit voice service providers from using other information or standards for setting attestation levels. We are concerned, in particular, about actual or 
                        <E T="03">de facto</E>
                         pay-for-attestation or attestation retribution or reward practices. This might occur, for example, if a provider tells a customer (whether an end user or upstream provider) that the customer may or must buy a particular product or service to receive a higher-level attestation or that the customer's attestations will be lowered if it does not take a specific action, notwithstanding what attestation would be proper for the call under the STIR/SHAKEN standards and the Commission's rules. We seek comment on this proposal. We do not intend to intervene in legitimate third-party-signer or similar arrangements. We seek comment on what legitimate arrangements may be implicated by this rule, and how to ensure our rule is cabined to exclude them. Would such a prohibition risk preventing providers from using advanced tools or strategies to help inform their attestation-level decisions? Do providers have evidence of such pay-for-attestation arrangements or retribution/reward schemes, and if so, are they a widespread problem? Are there other criteria on which providers rely in making attestation-level decisions that may or may not be useful to consider in this analysis?
                    </P>
                    <HD SOURCE="HD2">C. Closing STIR/SHAKEN Implementation Loopholes</HD>
                    <P>
                        The STIR/SHAKEN framework enables an end-to-end system for authenticating caller ID. For this system to work, the Identity header must travel the entire length of the call path, from originating provider to terminating provider, which can include networks of various types of voice service providers. The Commission has 
                        <PRTPAGE P="42616"/>
                        recognized that the existence of non-IP networks is among the most significant hinderances to full STIR/SHAKEN implementation and continues to explore avenues to advance the IP transition as well as its proposals for non-IP caller ID authentication solutions. The Commission's caller ID authentication rules apply to all voice service providers in a call path—namely voice service providers that perform the origination of calls, non-gateway intermediate providers that carry or process the calls without performing the origination or termination of them, gateway providers that receive calls from foreign originating or intermediate providers at their United States facilities and transmit them downstream, and voice service providers that perform the termination of calls. But we believe that certain providers do not consider themselves subject to the caller ID authentication rules based on perceived ambiguity in the definitions for these types of providers in the Commission's rules. We also believe at least one of the undue hardship implementation exemptions may no longer be needed. Additionally, providers that lack control of the network infrastructure necessary to implement STIR/SHAKEN currently do not have an obligation to participate in the STIR/SHAKEN ecosystem. Beyond these issues, we are concerned about other loopholes that may contribute to the number of calls that terminate without authentication information, including providers intentionally choosing to initiate or route authenticated calls over non-IP networks that cannot carry STIR/SHAKEN authentication information, providers accepting unauthenticated SIP calls, and our rule requiring only the first intermediate provider in a call path to authenticate an unauthenticated call. We propose to close these loopholes below and seek comment on any other steps we should take to enhance STIR/SHAKEN.
                    </P>
                    <HD SOURCE="HD3">1. Clarifying Definitions for Providers That Must Implement STIR/SHAKEN</HD>
                    <P>In this section, we examine a variety of terms and definitions found in our caller ID authentication rules and seek comment on a variety of proposals to amend or adopt definitions to ensure that our rules are precise, clear, administrable, and do not enable bad actor providers to skirt their obligations. Specifically, we seek to define important terms that describe all aspects of the transmission of a call, from the point it is initiated by a calling party to the point it is received by the call recipient, and all voice service provider types that play a role in this transmission. We believe that doing so will strengthen the caller ID authentication regulatory framework by putting all voice service providers on notice as to their precise obligations. We also anticipate this will strengthen our RMD regulatory framework, which requires, among other things, that providers identify their role in the call path and certify to their STIR/SHAKEN implementation for the type of provider they are and whether any exemptions apply. We intend for the definitions we adopt to apply on a call-by-call basis, and we seek comment on this approach. In connection with this task, we seek to know the universe of entities that participate in the voice ecosystem, the types of arrangements between these entities related to the provision of voice service, and whether the definitions we discuss below will indeed clarify the roles and obligations of each entity.</P>
                    <HD SOURCE="HD3">a. Voice Service and Voice Service Provider</HD>
                    <P>We propose to change our interpretations of the definitions of “voice service” in the RAY BAUM'S Act and the TRACED Act to encompass the same scope of providers, and propose to define “voice service provider” in reference to the “voice service” definition in the TRACED Act. We believe the harmonized interpretations represent the best reading of the definitions and will remove ambiguity concerning the applicability of the Commission's rules concerning illegal calls to providers.</P>
                    <P>
                        <E T="03">Statutory definitions of “voice service.”</E>
                         Congress has adopted two definitions of “voice service” that apply to the Commission's rules concerning illegal calls. The 2018 RAY BAUM'S Act defines “voice service” as “any service that is interconnected with the public switched telephone network and that furnishes voice communications to an end user using resources from the North American Numbering Plan or any successor to the North American Numbering Plan adopted by the Commission under Section 251(e)(1) of the Communications Act of 1934, as amended; and . . . [i]ncludes transmissions from a telephone facsimile machine, computer, or other device to a telephone facsimile machine.” The 2020 TRACED Act adopted an identical definition of “voice service,” except that it includes the language “[w]ithout limitation, any service that enables real-time, two-way voice communications, including any service that requires internet Protocol-compatible customer premises equipment and permits out-bound calling, whether or not the service is one-way or two-way voice over internet Protocol.” The Commission defines “interconnected VoIP service” in § 9.3 of its rules.
                    </P>
                    <P>
                        <E T="03">Inconsistent interpretations of the statutory definitions.</E>
                         Despite the nearly identical statutory language, the Commission's interpretation of each definition has differed, causing providers to be considered voice service providers for some of our rules pertaining to illegal calls and not for others. The Commission codified the earlier definition of “voice service” in the RAY BAUM'S Act in § 64.1600(r) of its rules and interpreted it broadly to encompasses all entities that originate, carry, or terminate voice calls through TDM, VoIP, or commercial mobile radio service. It has applied that definition to the Commission's telemarketing, Truth in Caller ID, call blocking, and ring signaling integrity rules. The Commission codified the later TRACED Act definition in § 64.6300(o), and interpreted it more narrowly to exclude intermediate providers. It has applied that definition to its caller ID authentication rules. In interpreting the TRACED Act's definition, the Commission did not discuss its prior interpretation of the RAY BAUM'S Act's definition, and only later acknowledged the divergence in interpretation.
                    </P>
                    <P>
                        <E T="03">Harmonizing the interpretations of “voice service.”</E>
                         We propose to conclude that the two “voice service” definitions cover the same scope of providers, and that the best reading of both definitions is to include intermediate providers. We believe the definitions cover the same scope of providers notwithstanding the added language in the TRACED Act's definition, because we believe that language merely provides more specificity as to what is included within the scope of “voice service” without expanding or narrowing the scope. We also believe that both definitions apply to the furnishing of voice communications to an end user directly or indirectly, such that all providers involved with an end user's voice communications, including intermediate providers, provide voice service to that end user. Both definitions require that voice communications be furnished to an end user, but we do not believe that the RAY BAUM'S Act or the TRACED Act expressly require the voice communications to be furnished 
                        <E T="03">directly</E>
                         or foreclose a reading that such voice communications may be furnished to an end user 
                        <E T="03">indirectly.</E>
                         Indeed, in one provision, the TRACED Act uses the term “voice service provider” to refer to providers that “originate 
                        <E T="03">or</E>
                         transmit” calls, suggesting that Congress intended the definition to include intermediate 
                        <PRTPAGE P="42617"/>
                        providers. We also maintain our understanding that “voice service” includes termination. We seek comment on this proposal and analysis.
                    </P>
                    <P>We do not believe that harmonizing the interpretation of these rules will change the scope of providers that are subject to any of our rules concerning illegal calls, and we seek comment on this view. While the proposed interpretation of the RAY BAUM's Act definition codified in § 64.1600(r) would effectively include within its scope, under our proposed interpretation, “any service that enables real-time, two-way voice communications, including any service that requires internet Protocol-compatible customer premises equipment and permits out-bound calling, whether or not the service is one-way or two-way voice over internet Protocol,” we believe those providers already fall within the scope of that definition and that our proposed interpretation will not subject any new providers to our telemarketing, Truth in Caller ID, call blocking, and ring signaling integrity rules. The proposed interpretation of the TRACED Act's definition codified in 64.6300(o) also will not change the scope of providers subject to our caller ID authentication rules because our rules already require intermediate providers to implement STIR/SHAKEN in their IP networks.</P>
                    <P>
                        <E T="03">Defining “voice service provider.”</E>
                         We also propose to adopt a definition of “voice service provider” as any entity that provides voice service for a given call. This will establish a consistent approach by having definitions for each category of provider, including the umbrella category for all voice service providers. It also would make clear that whether an entity is a voice service provider is determined on a call-by-call basis. We also reiterate that the term “voice service provider” includes all initiating, originating, intermediate, and terminating providers, including facilities-based providers and non-facilities-based providers, which includes VoIP resellers and MVNOs, and irrespective of whether the provider is claiming an exemption from the STIR/SHAKEN implementation obligation.
                    </P>
                    <P>
                        <E T="03">Conforming amendments to caller ID authentication rules.</E>
                         In connection with our proposal to streamline the Commission's caller ID authentication rules, we propose to rely on our proposed new interpretation of “voice service,” inclusive of intermediate providers and initiating providers (as we propose to define those below), for our caller ID authentication rules. Specifically, we propose to use the term “voice service provider” when a requirement applies to all categories of providers and to refer to specific categories of voice service providers when a requirement applies only to that category. We believe this specificity will facilitate our streamlining and add clarity to voice service providers' regulatory obligations depending on their position in a call path. We seek comment on this proposal and assessment.
                    </P>
                    <P>
                        <E T="03">Foreign voice service provider and domestic voice service provider.</E>
                         We propose to amend the definition of “foreign voice service provider” and establish a definition of “domestic voice service provider” to ensure that our proposed understanding of “voice service” does not lead to unintended confusion as to whether a provider is foreign or domestic and to deter bad actor foreign voice service providers from attempting to nominally establish themselves as domestic voice service providers to avoid scrutiny. Specifically, we propose to define “foreign voice service provider” as a voice service provider that was created, incorporated, or organized outside of the United States, regardless of whether it has an office, operation, or facilities in the United States. We also propose to define “domestic voice service provider” as a voice service provider that is not a foreign voice service provider. We believe that these changes are necessary because the current definition of “foreign voice service provider” is a provider that provides voice service “outside the United States.” Under our proposed understanding of voice service as furnishing voice communications to an end user both directly and indirectly, this means that any provider in the United States may be a “foreign voice service provider” so long as it terminates calls outside of the United States. We thus instead seek to tie the definition of “foreign voice service provider” to the business's location—where it was created, incorporated, or organized—rather than the nature of the service that it provides. We believe our proposed definition of “domestic voice service provider” as not a foreign voice service provider adequately covers the scope of providers that are created, incorporated, or organized within the United States. We also believe that these definitions will enable us to provide a clearer definition of “gateway provider,” as we propose to do below. We seek comment on these proposals.
                    </P>
                    <HD SOURCE="HD3">b. Initiation and Initiating Provider</HD>
                    <P>We propose to establish definitions of “initiation” and “initiating provider” for the purposes of our caller ID authentication rules to clarify the relationship of a customer to a voice service provider and to remove ambiguity as to which entity is responsible for each phase in the lifecycle of a call. Specifically, we propose to define “initiation” as “the action performed by a voice service customer in commencing a call, and does not include origination” and “initiating provider” as “a voice service provider that performs initiation for its end users' calls.”</P>
                    <P>We believe that adopting such definitions of “initiation” and “initiating provider” is likely necessary to enable us to better describe the action performed by a customer—such as an end user or a provider that serves end users—in placing a call, as distinct from the technological processes performed by the originating provider to enable that customer's call to traverse the voice network. In particular, under this definition, a non-facilities-based resale provider (as a customer of a facilities-based wholesale provider) that has a direct relationship with an end user would perform the “initiation” of a call on behalf of that end user, but the facilities-based wholesale provider would perform the “origination” of that call. When the facilities-based provider serves an end user directly (meaning the end user is the customer of the facilities-based provider), it would perform the “origination” of the end user's calls, while the end user would perform the “initiation.” We also believe that, according to this proposed definition, only the non-facilities-based provider that directly serves end users can be considered an initiating provider. Non-facilities-based providers in the middle of a chain of resellers would not fall within the definition, which we believe is appropriate given our understanding that they are not technologically in the path of a call. These providers would still be subject to the requirement to ensure the services they resell are not used to transmit illegal calls under § 64.1200(n)(5) of our rules, including the KYUP requirements we propose above.</P>
                    <P>
                        We also believe that the existence of ambiguity as to how the term “initiation” is used in the ATIS standards and in our orders suggests that adopting a definition is appropriate. For example, in the 
                        <E T="03">Eighth Caller ID Authentication Order,</E>
                         the Commission used the term “initiate” in one instance to differentiate the action that a voice service customer does from a voice service provider. The Commission described a complex call path in which an originating provider's customer is not 
                        <PRTPAGE P="42618"/>
                        the ultimate end user of a voice service, “such as where an originating service provider authenticates calls 
                        <E T="03">initiated</E>
                         by a reseller that itself maintains a direct relationship with the calling party.” However, given the lack of a codified definition in the Commission's rules or ATIS's standards, the Commission in the same 
                        <E T="03">Order</E>
                         also used the word as a synonym for origination. The ATIS standards appear to use the term in a similar way to our proposed definition, but limits its usage to customers that have a direct relationship with an originating provider. For example, ATIS-1000088 describes an “initiating [user agent]” that “signals the call to the originating [service provider]” and which is “typically in the possession of or under the control of a `customer,' which is typically an entity that has a direct commercial relationship with the originating [service provider] and may or may not be the ultimate source of the call (the end-user entity).” ATIS-1000088 at 9. This “SIP [User Agent]” is “authenticated by the originating service provider . . . network” and, “[w]hen the SIP [User Agent] is under direct management control of the [originating service provider], the [originating service provider's] network can assert the calling party identity in originating SIP INVITE requests initiated by the SIP [User Agent].”
                    </P>
                    <P>Do commenters agree that a definition of “initiation” and “initiating provider” is necessary to enable us to be more precise about exactly which actions or entities we are describing when discussing the initial stage in the life of a call? Should we adopt a different definition of “initiation,” such as only the action performed by a direct voice service customer of an originating provider? If so, how should we describe the action that is performed by the end user and the action performed by an end user's voice service provider that is not the customer of the originating provider? Should we instead define “initiate” as only the action performed by an end user in commencing a call? In that case, how should we define the action performed by the end user's voice service provider when it is not the originating provider? Do we need to establish a term and definition other than resale for the action that resellers in the middle of a chain of resellers perform? If yes, what should that term and definition be? Should we define initiation to include any such action?</P>
                    <HD SOURCE="HD3">c. Origination and Originating Provider</HD>
                    <P>We propose to establish a definition of “origination” for the purposes of our caller ID authentication rules to remove ambiguity as to voice service providers' obligations at this stage in a call path, and propose to define “originating provider” in reference to this definition. While the Commission has interpreted the word consistently with the ATIS standards when describing its caller ID authentication rules, we have not adopted a definition in our rules. Because of our proposal above to interpret “voice service” as including all providers that furnish voice communications to an end user, regardless of whether they furnish such service directly to the end user, we find it necessary to revise our caller ID authentication rules by replacing the term “voice service provider” with the term “originating provider” and/or “terminating provider” where appropriate.</P>
                    <P>
                        <E T="03">Commission precedent and ATIS standards.</E>
                         The Commission's caller ID authentication rules apply, as relevant here, to voice service providers that originate calls. ATIS-1000089 defines “originating service provider” as “[t]he service provider that handles the outgoing calls from a customer at the point at which they are entering the public network.” An originating provider may serve end user customers directly, or indirectly—such as through a voice service provider customer (
                        <E T="03">e.g.,</E>
                         a reseller or value-added service provider). In both circumstances, as stated in the ATIS standards and in the 
                        <E T="03">Eighth Caller ID Authentication Order,</E>
                         the originating provider is the entity that handles the call at the point at which it is entering the public network.
                    </P>
                    <P>
                        <E T="03">Need for establishing a definition of “origination.”</E>
                         We find that the absence of a specific definition of “origination” in our caller ID authentication rules has led to persistent industry confusion as to the scope of caller ID authentication obligations applicable to certain providers. On one end of the spectrum, for example, there appears to be some ambiguity as to whether an entity is a voice service provider (and therefore subject to caller ID authentication requirements) or is instead an end user. On the other end of the spectrum, although the Commission stated clearly in the 
                        <E T="03">Eighth Caller ID Authentication Order</E>
                         that a wholesale provider originating calls on behalf of a non-facilities-based reseller fulfills its own STIR/SHAKEN authentication obligation as an originating provider when signing the reseller's calls, some wholesale providers may nevertheless mistakenly consider themselves to be “intermediate” providers carrying their reseller customers' calls, and not originators of their resellers' calls. This misunderstanding of origination may cause a wholesale provider to think that it may apply only a C-level attestation, because the first criteria for both A- and B-level attestation is responsibility for origination. Another source of potential confusion may be that, outside of the Commission's caller ID authentication rules, the Commission has used the word “originate” or “origination” in a variety of different ways. Do commenters agree that confusion exists and is at least partly responsible for non-compliance with our caller ID authentication rules, including improper attestations? If so, do commenters agree that this confusion merits establishing definitions of “origination” and “originating provider” in our rules, or do commenters advocate for a different solution?
                    </P>
                    <P>
                        <E T="03">Definition of “origination” and “originating provider.”</E>
                         In the context of our caller ID authentication rules, we propose to define “origination” as the technological act of placing a customer's outgoing call onto the network using the voice service provider's own facilities, and “originating provider” as the voice service provider whose network performs the origination of a given call. We find that this definition is consistent with ATIS's usage, but also includes additional detail concerning the facilities used to place the call onto the network, which we believe is necessary to clear up industry confusion. Specifically, we find that tying origination to a technological act of placing a call onto the network using a voice service provider's own facilities means that a non-facilities-based provider cannot perform the “origination” of its customers' calls. As in the ATIS Technical Report, we use the term “customer” rather than “end user” to recognize instances when a facilities-based provider is originating calls on behalf of a non-facilities-based provider customer. We seek comment on our proposed definitions. Are they sufficiently clear to distinguish originating providers from intermediate providers that merely “carr[y] or process[ ] voice traffic”? Do commenters agree that a non-facilities-based provider cannot perform the “origination” of calls on behalf of its customers and that this is consistent with ATIS' usage of the term “origination”? If not, should we adopt a more expansive definition of “origination” to include when a call is “initiated” by a customer of a non-facilities-based provider, as we proposed to define “initiation” above? If so, should we use qualifying words to differentiate “types” of origination, such 
                        <PRTPAGE P="42619"/>
                        as “facilities-based origination” and “non-facilities-based origination”?
                    </P>
                    <HD SOURCE="HD3">d. Intermediate Provider, Gateway Provider, and Non-Gateway Intermediate Provider</HD>
                    <P>
                        <E T="03">Intermediate provider.</E>
                         We propose to modify the definition of “intermediate provider” in § 64.6300(g) of the Commission's rules only to account for the new definitions of “voice service provider,” “origination,” and “termination.” Specifically, we propose to change “any entity that carries or processes traffic that traverses or will traverse the public switched telephone network at any point” to a “voice service provider that carries or processes traffic” since the “voice service provider” definition captures the relationship of the traffic to the public switched telephone network. Additionally, we propose to change “originates” and “terminates” to “performs the origination or termination” to grammatically accommodate the newly proposed terms. We believe that the existing definition is otherwise sufficiently precise as to when a voice service provider is serving as an intermediate provider with respect to its caller ID authentication obligations, especially when coupled with the proposed definitions of “origination” and “termination.” We seek comment on this view. Does the definition, for example, prevent originating providers from claiming to be intermediate providers and thereby shirking their STIR/SHAKEN authentication obligations when handling calls from a non-facilities-based reseller customer?
                    </P>
                    <P>
                        <E T="03">Gateway provider.</E>
                         We propose to modify the definition of “gateway provider” in § 64.6300(d) of the Commission's rules to account for the new definitions of “domestic voice service provider” and “foreign voice service provider.” We believe that because the existing definition defines a gateway provider as a provider that has facilities located in the United States, it has incentivized bad actor foreign voice service providers to establish nominal facilities in the United States with the intent to avoid scrutiny by gateway providers when their calls enter the United States. Given that our proposed definition of “foreign voice service provider” refers to a voice service provider that was created, incorporated, or organized outside of the United States, regardless of whether it has an office, operation, or facilities in the United States, we believe that defining gateway provider in reference to the foreign voice service provider definition will more clearly delineate when a voice service provider is functioning as a gateway provider for any given call. We seek comment on this proposed definition. Should we modify the definition in a different way to ensure that bad actor foreign voice service providers cannot avoid scrutiny? For instance, NCLC argues that the existing definition “is underinclusive to the extent that some domestically originated calls will feature foreign calling parties either because a foreign participant is connected after an otherwise domestic call is answered or because a nominally domestic provider is in fact operating as a foreign proxy.” It requests that the Commission define “foreign-originated call” as “any call received from a `foreign originating provider or foreign intermediate provider.'” Does our proposed definition resolve NCLC's concern? If not, should we adopt a definition of “foreign originated call” as NCLC proposes? We note that the Commission declined to adopt a similar proposal when it first established the “gateway provider” definition.
                    </P>
                    <P>
                        <E T="03">Non-gateway intermediate provider.</E>
                         We believe that the definition of “non-gateway intermediate provider” in § 64.6300(i) of the Commission's rules is sufficiently precise as to when a voice service provider is serving as a non-gateway intermediate provider with respect to its caller ID authentication obligations that we propose to leave it substantively unaltered, and we seek comment on this proposal.
                    </P>
                    <HD SOURCE="HD3">e. Termination and Terminating Provider</HD>
                    <P>To remove ambiguity as to voice service providers' obligations at the final stage in a call path, we propose to establish a definition of “termination” for the purposes of our caller ID authentication rules and propose to define “terminating provider” in reference to this definition. Specifically, we propose to define “termination” as the technological act of serving to a customer an incoming call received on a voice service provider's own facilities that are interconnected with the public network, and “terminating provider” as the voice service provider whose network performs the termination of a given call. We believe that this proposed definition is consistent with ATIS's definition. Under the STIR/SHAKEN framework and the Commission's rules, terminating providers are responsible for performing the SHAKEN verification function to ensure that the caller ID associated with the call it terminates was properly authenticated. We believe that tying termination to the technological act of serving a call received on the provider's own facilities makes clear that a non-facilities-based provider does not “terminate” calls for its end users. As in the definition of “origination,” we use the term “customer” rather than “end user” to preserve the possibility of a facilities-based provider terminating calls on behalf of a non-facilities-based provider customer. We seek comment on this definition. Do commenters agree that our definition should be limited to our caller ID authentication rules? Do commenters agree that, under the ATIS standards, a non-facilities-based provider cannot “terminate” calls on behalf of its end users? Should we instead adopt a more expansive definition of “termination” to include service of an incoming call to an end user by a non-facilities-based provider? For example, should we use “termination” in a generic sense as the “end point of service” of an incoming call along with qualifying words to differentiate “types” of termination, such as “end user termination” or “facilities-based termination”?</P>
                    <HD SOURCE="HD3">f. Facilities-Based Provider and Non-Facilities-Based Provider</HD>
                    <P>
                        To ensure that providers know whether they have an obligation to implement STIR/SHAKEN or are subject to the implementation exemption for providers that lack control of the network infrastructure necessary to implement STIR/SHAKEN (hereafter the “non-facilities-based provider implementation exemption”), we: (1) propose to define the terms “facilities-based provider” and “non-facilities-based provider” for the purposes of our caller ID authentication rules and seek comment on how best to do so; and (2) propose to codify and clarify the non-facilities-based provider implementation exemption as it relates to those terms. The Commission has previously only given limited guidance on what it means to “lack control of the network infrastructure.” Our intent with these proposals therefore is to make clear which providers may claim the “non-facilities-based provider exemption” by: 
                        <E T="03">first,</E>
                         clarifying what it means to be a “non-facilities-based provider”; and 
                        <E T="03">second,</E>
                         clarifying what it means to lack control of the network infrastructure necessary to implement STIR/SHAKEN. Although non-facilities-based providers do not have a STIR/SHAKEN implementation obligation under the exemption, we put them on notice that, to the extent they serve end users directly, they may nevertheless have STIR/SHAKEN-related duties under our separate proposal to require that all voice service providers that serve end users directly (including non-
                        <PRTPAGE P="42620"/>
                        facilities-based providers) make attestation-level decisions for their end users' SIP calls.
                    </P>
                    <P>
                        <E T="03">Defining “facilities-based provider” and “non-facilities-based provider.”</E>
                         As a starting point for defining “facilities-based provider” and “non-facilities-based provider,” we believe the definitions should reflect the following assumptions:
                    </P>
                    <P>
                        <E T="03">First,</E>
                         we believe we should define these terms without reference to the facilities' ability to carry STIR/SHAKEN authentication information to reflect that a voice service provider can also be a facilities-based provider when it provides voice service over its own non-IP networks.
                    </P>
                    <P>
                        <E T="03">Second,</E>
                         we believe that “facilities” refers to network infrastructure, such as physical elements (
                        <E T="03">e.g.,</E>
                         switches, routers, copper wires, fiber wires, spectrum, wireless transmitters and receivers, and satellites) and any software, services, or facilities used to operate those physical elements.
                    </P>
                    <P>
                        <E T="03">Third,</E>
                         we believe a facilities-based provider is one that owns and operates or leases and operates the network infrastructure, and therefore “controls” those elements.
                    </P>
                    <P>
                        <E T="03">Fourth,</E>
                         we believe that whether a provider is facilities-based or non-facilities-based is circumstantial, not conditional, meaning that a provider may be facilities-based in some circumstances and not in others.
                    </P>
                    <P>
                        We seek comment on these views. We also seek comment on whether we should incorporate a fifth assumption based on the relationship a provider has with end users, and if so, what that assumption should be. For example, the definition of “facilities-based provider” in our FCC Form 477 rules describes such providers as entities with facilities that terminate at end user premises. In the 
                        <E T="03">Fourth Caller ID Authentication Order,</E>
                         87 FR 3684 (Jan. 25, 2022), the Commission implicitly adopted a similar, but narrower definition of “facilities-based,” as relating to the last-mile connection between the voice service provider's network and an end user. Specifically, as part of its determination that “non-facilities-based small voice service providers” “must implement STIR/SHAKEN in the IP portions of their network,” the Commission “define[d] a voice service provider as `non-facilities-based' if it offers voice service to end-users solely using connections that are not sold by the provider or its affiliates.” It adopted this definition because it “captures those providers that lack facilities-based voice connections [and] provides certainty to both affected voice service providers and the Commission.” It stated that “[a] voice service provider's voice service that does not use connections sold by the provider or its affiliates, by definition, `rides atop' another provider's transmission service. Therefore, such voice service is not offered over the voice service provider's own facilities.” The Commission noted that a voice service provider “readily knows whether it is offering voice service that relies on its own (or its affiliates') facilities . . . , and therefore can easily determine whether it is subject to this definition.” In other words, for example, a provider that owns a switch that it uses to provide voice service but does not own the fiber wire that connects the switch to the end user would be a non-facilities-based provider under that definition. Should one of these approaches be reflected in a fifth assumption? Conversely, we note that our existing definition of “gateway provider” includes a reference to such providers' facilities, even though those facilities may not connect with end users, suggesting that intermediate providers could qualify as a facilities-based provider. Should we follow this approach and simply decline to adopt a fifth assumption?
                    </P>
                    <P>We also seek comment on whether our assumptions as to how “facilities-based” should be defined are valid with respect to all voice service providers that should be obligated to implement STIR/SHAKEN. Do the assumptions hold true for all originating, intermediate, and terminating providers as we propose to define those terms above? For example, given our proposal to include “facilities” in the definition of “origination,” do commenters agree that a non-facilities-based provider cannot and should not be considered an originating provider? If so, and thus all originating providers are “facilities-based,” are our assumptions accurate as to all originating providers? We also seek comment on whether our assumptions about what “facilities-based” should mean are true for other types of providers. For example, do our assumptions describe some or all VoIP resellers and MVNOs? What about PBXs (hosted or otherwise), dialing platforms, cloud service providers, over-the-top service providers, call centers, value-added-service providers, or TNSPs? Our understanding is that these arrangements are captured by terms like unified communications as a service (UCaaS), communications platform as a service (CPaaS), and contact center as a service (CCaaS), but we seek comment on the best shorthand terminology to use to refer to these types of arrangements.</P>
                    <P>
                        If commenters agree with our proposed assumptions about “facilities-based providers,” how should we distill such assumptions into a definition of “facilities-based provider” and “non-facilities-based provider” for the purposes of our caller ID authentication rules? If we should assume that a facilities-based provider has a relationship with an end user, would the existing definition in our FCC Form 477 rules satisfy all five of the assumptions? We note that in the 
                        <E T="03">Fourth Caller ID Authentication Order,</E>
                         the Commission declined to adopt a similar definition to that in our FCC Form 477 rules because it would place a higher compliance obligation on small voice service providers to determine whether they meet its terms compared to the Commission's more straightforward definition. Should we instead adopt a definition that follows the “non-facilities-based small voice service provider” definition adopted in the 
                        <E T="03">Fourth Caller ID Authentication Order</E>
                        ? If we decline to assume that a facilities-based provider has a relationship with an end user, should we adopt a definition of “facilities-based provider” that includes any provider with facilities used in the call path, including intermediate providers? If we do not adopt a definition consistent with the “non-facilities-based small voice service provider” definition in the 
                        <E T="03">Fourth Caller ID Authentication Order,</E>
                         is it necessary to modify our rules to clarify the implementation obligation for such providers in light of the fact that the implementation exemption for such providers has expired? If our assumptions describe any providers that should not be obligated to implement STIR/SHAKEN, how should we define “facilities-based-provider” and/or “non-facilities-based provider” to exclude such providers? For example, should we define “non-facilities-based provider” simply as “a provider that is not a facilities-based provider”? Or, should we also include in the definition of “non-facilities-based provider” additional types of providers that otherwise would have satisfied a definition of “facilities-based provider” in order to ensure they qualify for the non-facilities-based provider exemption?
                    </P>
                    <P>
                        <E T="03">Codification of non-facilities-based provider exemption.</E>
                         We propose to codify in our rules an exemption from implementing STIR/SHAKEN for non-facilities-based providers, however we define that term, which the Commission has thus far referred to as an exemption for providers that lack control of the network infrastructure necessary to 
                        <PRTPAGE P="42621"/>
                        implement STIR/SHAKEN. This exemption only relates to providers whose calls are originated in IP and “is distinct from the Commission's continuous extension for non-IP portions of a provider's network.” Although the Commission first acknowledged this exemption in the 
                        <E T="03">First Caller ID Authentication Order,</E>
                         it has not codified the exemption in its rules or fully explained its scope, which we believe has resulted in industry confusion. In proposing to codify the exemption, we seek to resolve this confusion. However, providers may claim the exemption if they certify to partial or no STIR/SHAKEN implementation in their RMD filing, so long as they explain in detail how it applies to them.
                    </P>
                    <P>As an initial matter, we believe this exemption is inherent in the STIR/SHAKEN framework and implicitly adopted in the TRACED Act. Because the STIR/SHAKEN framework relies on the transmission of information in the Identity header of the SIP INVITE, it only operates on the IP portions of a voice service provider's network. Our rules, mirroring the TRACED Act, therefore only require voice service providers to implement the STIR/SHAKEN authentication framework in the IP portions of their networks. That is, because STIR/SHAKEN only works in IP networks, only facilities-based voice service providers that have IP-based facilities used for voice service on which they can install STIR/SHAKEN solutions are subject to this implementation requirement. If a provider does not have IP-based facilities for voice services on which it can install STIR/SHAKEN solutions, it cannot technically implement STIR/SHAKEN and therefore does not have an implementation obligation.</P>
                    <P>
                        We also believe the scope of the exemption is clarified based on the second and third assumptions we set out above about facilities-based providers and non-facilities-based providers. We believe that part of the confusion about the scope of the existing exemption stems from a lack of guidance from the Commission as to the meaning of “network infrastructure” and “control.” The 
                        <E T="03">Eighth Caller ID Authentication Order</E>
                         gave one example of “network infrastructure,” namely “switches for voice service in the IP portion of their network.” Under the second assumption, we describe network infrastructure as including physical elements (
                        <E T="03">e.g.,</E>
                         switches, routers, copper wires, fiber wires, spectrum, wireless transmitters and receivers, and satellites) and any software, services, or facilities used to operate those physical elements. Under the third assumption, we describe facilities-based providers as having “control” over the network infrastructure, which we describe as owning and operating or leasing and operating the network infrastructure. Essentially, mere operation, therefore, would not give a provider sufficient authority over the network infrastructure such that it could implement STIR/SHAKEN thereon. When viewed together, we believe a customer (including a non-facilities-based provider) that purchases services from a facilities-based provider is simply a user of the facilities-based provider's network infrastructure and cannot own or control the network infrastructure necessary to implement STIR/SHAKEN. We further believe that a facilities-based provider cannot give control of its network infrastructure to a non-facilities-based provider (and thereby essentially turn a non-facilities-based provider into a facilities-based provider) by, for example, providing the non-facilities-based provider with access to software that enables them to enter attestations and certificate information for the purpose of authentication. In other words, we do not believe a facilities-based provider can establish a STIR/SHAKEN implementation obligation for another provider by virtue of the services it provides. In contrast, we believe that a provider ceases to be a facilities-based provider—and thus, ceases to have a STIR/SHAKEN implementation obligation—with respect to network infrastructure over which it has ceded authority, such as by leasing the network infrastructure to another provider. We seek comment on these views. If we decline to follow the meanings of “facilities-based” and “non-facilities-based” used in the 
                        <E T="03">Fourth Caller ID Authentication Order,</E>
                         could a provider be facilities-based for the purposes of that 
                        <E T="03">Order</E>
                         but non-facilities-based for the purposes of this exemption? If so, do we need to resolve that issue given that the “non-facilities-based provider” extension in the 
                        <E T="03">Order</E>
                         has lapsed?
                    </P>
                    <P>
                        Given the express limitation of our STIR/SHAKEN implementation obligation to a voice service provider's IP networks, codification of the exemption may not be strictly necessary, but we now believe doing so will promote regulatory clarity. In the 
                        <E T="03">Call Branding FNPRM,</E>
                         we sought comment on whether and how to repeal the exemption. Upon further evaluation, we do not believe the exemption can be repealed because it is a necessary outcome of the fact that STIR/SHAKEN can only be implemented in IP networks. We seek comment on our proposal and beliefs. Is the scope of the exemption sufficiently clear? Are there any potential downsides or unintended consequences to codification? We stress our view that the exemption is not status-based, but circumstantial. That is, if a provider is facilities-based in some circumstances (such as with respect to certain calls) and not in others, it has an implementation obligation in the former circumstance and not the latter. We invite comment on these proposed conclusions and analysis.
                    </P>
                    <HD SOURCE="HD3">g. Upstream and Downstream</HD>
                    <P>Given confusion in the record, and their importance in determining caller ID authentication and KYUP obligations, we propose to define the terms “upstream” and “downstream” for the purposes of our caller ID authentication rules. Specifically, we propose to define “upstream” as nearer to the source of a call, and “downstream” as nearer to the destination of a call. This usage accords with the definitions given for the words in the dictionary as applied to a stream or river. Thus, as applied to providers, an “upstream provider” is a provider that is closer to the source of the call, and a “downstream provider” is closer to the destination of the call. We are careful to not conflate the “source” of a call with the “origination point” of a call, as the ATIS standards consider non-facilities-based providers that are near the source of the call to be “upstream” of the facilities-based providers that originate the calls, for example. While undefined in the Commission's rules, the rules use the term “upstream” consistently with our proposed definition. Similarly undefined in the Commission's rules, our proposed definition of “downstream” accords with existing rules that use the term. We seek comment on our proposed definitions.</P>
                    <HD SOURCE="HD3">h. Customer and End User</HD>
                    <P>
                        To remove ambiguity and ensure that voice service providers understand their regulatory obligations, we propose to define the terms “customer” and “end user” for the purposes of our caller ID authentication rules. Specifically, we propose to define “customer” as any individual or entity that purchases voice service from a voice service provider, and “end user” as the ultimate consumer of voice service. The ATIS-1000088 Technical Report defines “customer” as “[t]ypically a service provider's subscriber, which may or may not be the ultimate end-user of the 
                        <PRTPAGE P="42622"/>
                        telecommunications service.” Under this definition, a customer “may be a person, enterprise, reseller, or value-added service provider.” In the 
                        <E T="03">Eighth Caller ID Authentication Order,</E>
                         the Commission declined to adopt a definition of “customer” that means “solely the end user that initiated the voice service,” as was suggested by certain commenters, because it was not necessary to do so for the purposes of the third-party authentication rules it adopted in that 
                        <E T="03">Order.</E>
                         In doing so, however, it noted that such a definition “would be a significant departure from a plain reading of the ATIS standards and reference documents, and could be disruptive to the use cases that those standards and reference documents clearly contemplate as functioning within the STIR/SHAKEN ecosystem.” We believe our proposed definition is consistent with this determination and ATIS's usage, and seek comment on this belief. Regarding “end user,” ATIS defines the term as “[t]he entity ultimately consuming the VoIP-based telecommunications service,” which may be “the direct customer of [an originating] service provider or may indirectly use the VoIP-based telecommunications service through another entity such as a reseller or value-added service provider.” The 
                        <E T="03">Eighth Caller ID Authentication Order</E>
                         also affirmed—but did not codify—this understanding of “end user.” ATIS-1000088, therefore, makes clear that, in some cases, the “customer” and “end user” are not the same. According to ATIS-1000088, end users may include individual or enterprise subscribers, including enterprise PBXs. We believe that our proposed definition is consistent with ATIS-1000088. We also believe that our proposed definition of “end user” is consistent with our definition of the term for the purposes of FCC Form 477. We seek comment on our proposed definitions. Should we instead define “end user” with a cross reference to § 1.7001(a)(3) of our rules?
                    </P>
                    <HD SOURCE="HD3">i. Additional Guidance</HD>
                    <P>
                        Given the complexity of arrangements related to the provision of voice service, we are cognizant that entities may desire even more certainty regarding their role in providing such service. Although we believe the definitional changes we propose above should resolve supposed ambiguity as to each entity's role in the provision of voice service, and thereby bring clarity regarding each voice service providers' obligations under our rules, we seek comment on whether we should establish a mechanism that would allow for faster resolution of uncertainty, should any remain. In the 
                        <E T="03">Eighth Caller ID Authentication Order,</E>
                         we declined ZipDX's request to provide clarification regarding the operation of our rules, including applicable KYC requirements, in a variety of hypothetical caller ID authentication scenarios, finding that such guidance would be unproductive in the absence of a more focused record. We seek comment now on whether establishing a procedural mechanism would facilitate such additional guidance in the future. This, we believe, would both benefit entities and advance the Commission's goal to ensure that all voice service providers are meeting their obligations. We therefore seek comment on whether we should delegate authority to the Bureau to issue guidance to the extent further definitional clarification is needed, such as in the form of a Frequently Asked Questions document or Public Notice. Should we instead establish a process by which entities may request a non-binding advisory opinion from the Bureau regarding whether they are a voice service provider and if so, which category of voice service provider they are for the services they provide for each type of call they transmit? Are any such mechanisms necessary given the definitional improvements we propose above?
                    </P>
                    <HD SOURCE="HD3">2. Repealing STIR/SHAKEN Implementation Extensions</HD>
                    <P>
                        We propose to repeal one of the two remaining undue hardship extensions to STIR/SHAKEN implementation to further advance ubiquitous deployment of the framework, and seek comment on whether to repeal the second remaining extension and whether any new or narrower extensions may be appropriate. The TRACED Act empowers the Commission to grant classes of voice service providers and types of calls extensions to STIR/SHAKEN implementation on the basis of undue hardship. Because STIR/SHAKEN only works on IP-based voice networks, the TRACED Act also grants an ongoing implementation extension for the portions of a provider's network that rely on technology that cannot initiate, maintain, carry, process, and terminate SIP calls (
                        <E T="03">i.e.,</E>
                         non-IP networks). That extension is not relevant to our discussion here. The Commission has previously assessed whether STIR/SHAKEN implementation would cause “undue hardship” by balancing the “burdens and barriers to implementation” with the benefit to the public of implementing STIR/SHAKEN expeditiously. Pursuant to the TRACED Act's directive, the Commission has granted and maintained two ongoing undue hardship extensions for: (1) voice service providers that cannot obtain the SPC token necessary to participate in STIR/SHAKEN due to the Governance Authority's policy for obtaining a token; and (2) small voice service providers that originate calls via satellite using NANP numbers. If a voice service provider certifies to less than full STIR/SHAKEN implementation as part of its obligation to certify to its STIR/SHAKEN implementation status in its RMD filing, it “must both explicitly state the rule that exempts it from compliance and explain in detail why that exemption applies.” The TRACED Act also directs the Commission to address any issues that formed the basis for any undue hardship extensions it has granted and “enable as promptly as reasonable full participation of all classes of providers of voice service and types of voice calls to receive the highest level of trust.” In the absence of undue hardship, there is no basis to maintain an extension. We believe that there is no longer an undue hardship for the SPC token extension, and therefore that the extension is no longer needed. We also seek comment on whether there is any undue hardship to STIR/SHAKEN implementation that justifies maintaining the extension for small providers originating calls via satellite using NANP numbers.
                    </P>
                    <P>
                        <E T="03">SPC token extension.</E>
                         We believe that all providers that meet the voice service provider definition and have an existing obligation to implement STIR/SHAKEN are able to obtain SPC tokens without undue hardship, and therefore propose to repeal the extension for voice service providers that cannot obtain an SPC token due to the Governance Authority policy. Below, we acknowledge that certain VRS providers assert in comments responding to the 
                        <E T="03">Call Branding FNPRM</E>
                         that they are unable to obtain SPC tokens, in connection with assertions that they do not meet the definition of voice service provider or qualify for the non-facilities-based provider exemption. We seek comment there on whether we should establish a new undue hardship extension for such providers in the event we find they do have a STIR/SHAKEN implementation obligation. In the March 2023 
                        <E T="03">Sixth Caller ID Authentication Order,</E>
                         88 FR 40096 (June 21, 2023), the Commission sought comment on whether to eliminate the SPC token extension based on the Bureau's finding in its December 2022 
                        <E T="03">Annual Evaluation of STIR/SHAKEN Implementation Extensions</E>
                         that token access no longer stood “as a significant barrier to full participation in STIR/SHAKEN.” In the November 2024 
                        <PRTPAGE P="42623"/>
                        <E T="03">Eighth Caller ID Authentication Order</E>
                         that the Commission adopted based on that record, it held off on modifying the extension because the Bureau was still performing a review of submissions in the RMD claiming the extension, the results of which it believed would better inform its decision on the matter. In its December 2025 
                        <E T="03">Annual Evaluation of STIR/SHAKEN Implementation Extensions,</E>
                         the Bureau “tentatively [found] that the extension for providers that are incapable of obtaining an SPC token may no longer be necessary” based in part on Bureau staff's initial assessment of RMD submissions. The Bureau nevertheless concluded that the extension remained necessary so that it could complete its evaluation of RMD submissions claiming the extension.
                    </P>
                    <P>Bureau staff has now completed that assessment, and we believe repeal of the extension is warranted based on the Bureau's findings. The Bureau identified 338 filings—3.2% of all the filings in the database at the time of review—that affirmatively assert the exemption, but that it does not believe “explain[ed] in detail why the exemption applies,” as they are required to do.</P>
                    <P>The Bureau's calculation does not include filings explaining that the provider is in the process of obtaining an SPC token, filings that merely state the provider does not have an SPC token without claiming that the provider is unable to obtain one, or filings submitted by providers that appear on the STI-PA list of authorized providers. Specifically, 272 filers asserted, in relation to claiming the SPC token exemption, that they lack control over the network infrastructure necessary to implement STIR/SHAKEN, but that constitutes a separate exemption. For another 57, the Bureau does not believe the justifications supplied are sufficient, such as the steps the provider took to “diligently pursue” obtaining a token. For instance, some providers say they are not required to submit a Form 499—a requirement to obtain an SPC token—but fail to explain why they are not required to if they are a voice service provider that must implement STIR/SHAKEN. Other providers say they cannot obtain an operating company number (OCN) from NECA—another requirement to obtain a token—but do not explain the steps they took to obtain an OCN and whether they were denied and why. Others still note they are relying on their downstream provider to authenticate calls or lack numbering resources to obtain an SPC token, which are both invalid justifications. The remaining filings claiming the exemption are TRS providers, which we address separately below and do not believe bear on whether we should repeal this exemption. In the absence of any stated reasons why voice service providers cannot meet the token access policy, we do not believe there is any undue hardship basis for maintaining the SPC token extension. We seek comment on this proposal and our assessment, including whether any voice service provider has attempted to obtain an SPC token and been denied, and the reasons why.</P>
                    <P>
                        <E T="03">Small providers originating calls via satellite using NANP numbers.</E>
                         We seek comment on whether there is any undue hardship to STIR/SHAKEN implementation that warrants maintaining the extension for small voice service providers that originate calls via satellite using NANP numbers. We do seek to alter our conclusion that “satellite providers that do not use NANP numbers to originate calls or only use such numbers to forward calls to non-NANP numbers are not `voice service providers' under the TRACED Act and therefore do not have a STIR/SHAKEN implementation obligation.” When the Commission established the extension in the 
                        <E T="03">Sixth Caller ID Authentication Order,</E>
                         it did so on the basis that “the number of satellite subscribers using NANP resources `is min[u]scule' ” and “that there is little evidence that satellite providers or their users are responsible for illegal robocalls,” in part because “satellite service costs make the high-volume calling necessary for robocallers uneconomical.” Upon further consideration, we do not believe that either of these justifications describe barriers or burdens to STIR/SHAKEN implementation for these small providers. In the absence of barriers or burdens, and in light of the TRACED Act's command that the Commission “enable as promptly as reasonable full participation of all classes of providers of voice service and types of voice calls to receive the highest level of trust,” as well as the growth in satellite connectivity, we believe repealing this undue hardship extension may be appropriate. However, we invite comment on whether there are indeed any barriers or burdens to STIR/SHAKEN implementation, what they are, and how they balance against the benefits of full implementation. We encourage commenters to be specific about any such barriers or burdens, including whether and why it is technically impossible or prohibitively costly for such providers to implement STIR/SHAKEN. We also seek comment on whether such barriers and burdens apply to all satellite providers and types of satellite voice services equally, and if not, whether we should narrow the extension to exclude certain providers or types of service. We note that only nine providers have claimed the extension in the RMD. Commenters should describe the specific operational or technical components of the network architecture that may prevent deployment or implementation of the STIR/SHAKEN framework on the satellite voice network. Additionally, we seek comment on how satellite calls using NANP numbers that originate from such providers are treated in the STIR/SHAKEN ecosystem today. Are they being authenticated by downstream providers, and if so, what attestation level are such calls receiving? If we maintain the extension for some or all small satellite providers, would it undermine the integrity of the STIR/SHAKEN ecosystem that we otherwise seek to strengthen in this proceeding? Would such potential harms be mitigated if we require satellite voice service providers to follow our proposal below that all voice service providers that serve end users directly make attestation-level decisions for their end users' SIP calls? Additionally, we seek comment on whether and how repealing the extension for satellite voice service providers at this time may interact or interfere with ongoing deployment of satellite voice service networks or compliance with regulatory obligations under the Commission's rules or otherwise.
                    </P>
                    <P>
                        <E T="03">Need for new extensions.</E>
                         Given the TRACED Act's direction for the Commission to achieve full STIR/SHAKEN deployment and that many of the measures herein are geared toward that outcome, we do not believe that new undue hardship extensions are appropriate. We also do not believe that the proposed definitional clarifications above would impose an implementation obligation on any classes of providers that were not already required to implement STIR/SHAKEN. Nevertheless, we seek comment on whether our proposed clarifications do make any entities newly aware of their implementation obligation and whether there are barriers or burdens to implementation of STIR/SHAKEN that would pose an undue hardship.
                    </P>
                    <HD SOURCE="HD3">3. Requiring Providers Serving End Users Directly To Assign Attestations</HD>
                    <P>
                        To make STIR/SHAKEN a more valuable resource for caller ID information, and thereby reduce the vectors for bad actors to put spoofed calls on the voice network, we propose to require all voice service providers 
                        <PRTPAGE P="42624"/>
                        that serve end users directly to make attestation-level decisions for their end users' SIP calls. Under existing conditions, the originating provider, as the facilities-based provider, is supposed to authenticate calls initiated by the non-facilities-based-provider using the originating provider's certificate with an attestation based on its knowledge of the non-facilities-based provider. We further propose to require originating providers to authenticate such calls (whether themselves or through a third-party) using the attestation-level decisions of the provider serving end users directly. This proposal would not change the obligations for originating providers when they serve end users directly; they will continue to be required to authenticate such calls using their own attestation-level decisions. This proposal would, however, add an obligation for initiating providers—
                        <E T="03">i.e.,</E>
                         non-facilities-based voice service providers that serve end users directly—by requiring them to make attestation-level decisions regarding their end users' SIP calls and for originating providers that perform the origination of such calls by requiring them to authenticate the calls with the attestation level selected by the initiating provider. We believe that if we adopt this proposal, every voice service provider that has a relationship with a call that is originated in IP will be participating in the STIR/SHAKEN ecosystem. We also believe this proposal will close the knowledge gap that exists when the originating provider does not have a direct relationship with the end user because the end user obtained voice service from an intermediary provider, such as a reseller (
                        <E T="03">i.e.,</E>
                         a non-facilities-based provider). This is the knowledge gap described as Scenario 2 above. We seek comment on this proposal and analysis. If we adopt this proposal, are there any voice service providers that would remain not subject to a STIR/SHAKEN-related obligation related to SIP calls? If so, which providers? Are there any providers we should exempt from the attestation obligation, and if so, why?
                    </P>
                    <P>
                        <E T="03">Mechanism for implementation.</E>
                         We seek comment on whether we should designate one or more mechanisms to ensure that originating providers apply initiating providers' attestation-level decisions when authenticating calls, and if so, which mechanism(s) we should designate. Should we permit or require the use of delegate certificates, which we propose above to find are valid mechanisms for this purpose? Should we instead require initiating providers to obtain an SPC token, use that token to obtain certificates, make all STIR/SHAKEN attestation-level decisions regarding calls initiated by their end users, and ensure originating providers sign calls with the initiating provider's certificate and attestation-level decision, similar to our third-party authentication rule? While the Commission adopted a rule in the 
                        <E T="03">Eighth Caller ID Authentication Order</E>
                         permitting voice service providers with a STIR/SHAKEN implementation obligation to engage a third party to perform on their behalf the technological act of signing the calls they originate, it declined to consider those providers that lack control over the network infrastructure necessary to implement STIR/SHAKEN as “originating service providers” and thus “first parties” for the purposes of third-party authentication. It concluded that such a definition would conflict with the text of the Commission's rules establishing the scope of providers subject to the STIR/SHAKEN implementation obligation and would be inconsistent with how the ATIS standards and technical reports use that term. The Commission did, however, acknowledge that some resellers voluntarily attempt to authenticate caller ID information despite not having control over the network infrastructure necessary to implement STIR/SHAKEN (and, thus, lacking a STIR/SHAKEN implementation obligation) by relying on their wholesale providers to sign their calls. The Commission therefore encouraged, but did not require, such resellers to provide their wholesalers with enough information to enable the wholesalers to determine the appropriate attestation level of the calls initiated by the resellers' end users, pursuant to the wholesalers' obligations as originating providers under the Commission's rules and the STIR/SHAKEN standards. To our knowledge, there are no barriers or burdens to non-facilities-based providers obtaining an SPC token under the existing Governance Authority policy, and we believe requiring this would have the benefit of subjecting resellers to the same vetting that originating providers must undergo to obtain an SPC token. Consistently, ZipDX asserts that resellers that lack control of the infrastructure necessary to implement STIR/SHAKEN would be able to obtain an SPC token of their own should we require them to do so. Is that accurate? If not, what are the barriers and burdens, and do they warrant extending the compliance deadline to account for them? Should we require the Governance Authority to change its policy? How would our proposed approach work when there are multiple levels of resale, given that the initiating provider may not have a direct relationship with the originating provider? We also seek comment on whether we should require the use of specific mechanisms in different circumstances and the reasons for doing so. Additionally, we seek comment on the feasibility for initiating providers to implement any mechanisms.
                    </P>
                    <P>
                        <E T="03">Impact on other providers.</E>
                         We seek comment on any other impacts our proposal may have on voice service providers that bear a connection to a call. What obligations, if any, should we attach to non-facilities-based providers when they are not serving end users directly, such as when they are a reseller in a multi-level resale chain, aside from any existing and proposed requirements? Should they be held responsible if the initiating provider does not assign attestations to calls or applies an improper attestation? Likewise, should a TNSP that assigns numbers to a non-facilities-based provider be held responsible when the non-facilities-based provider further assigns those numbers to an initiating provider that fails to properly follow the attestation requirements? Should an originating provider that is not the TNSP also be held responsible for mis-attested calls? Would these various threads of liability be connected through tracebacks and the KYUP proposals above? If an originating provider uses a third-party to perform the technical act of signing a call that must be authenticated with the attestation level selected by an initiating provider, what obligations should the initiating provider have in that signing arrangement, if any? What impact, if any, will our proposal have on the ability for terminating providers to verify calls if they are attested to by an initiating provider and/or authenticated with an initiating provider's certificate? What will be the impact on industry traceback efforts?
                    </P>
                    <P>
                        <E T="03">Issues related to use of initiating provider attestations.</E>
                         Regardless of the mechanism(s) we choose, we seek comment on feasibility and other issues that may arise with requiring originating providers to use the attestation level designated by the initiating provider. We note that under ATIS-1000074, a voice service provider may only apply an A- or B-level attestation when it is responsible for originating the call onto the IP network. Would it be permissible under the ATIS standards for initiating providers to apply an A- or B-level attestation? Should we modify the 
                        <PRTPAGE P="42625"/>
                        attestation criteria to make it permissible? We also note that the ATIS standards contemplate that the originating provider will always remain the ultimate authority in assigning attestation levels. Is it permissible under the standard for the originating provider to apply the attestation selected by the initiating provider, and if not, should we adopt a rule making it permissible? Does requiring the originating provider to apply the attestation level selected by the initiating provider raise concerns regarding the validity of the attestation decision? For instance, under the mechanism where the initiating provider obtains its own SPC token and certificates from the Governance Authority, the originating provider could be required to authenticate a call with an A-level attestation designated by the initiating provider when the originating provider has no knowledge regarding whether there is a legitimate association between the end user and the number being used. Is this a valid concern? Should we maintain the requirement for originating providers to make the ultimate attestation decision based on their own determinations of the attestation criteria? If so, would it still be worthwhile to require that initiating providers obtain their own SPC token and certificates and therefore undergo the vetting and oversight associated with the Governance Authority's token access and token revocation policies?
                    </P>
                    <HD SOURCE="HD3">4. Ensuring Calls Are Authenticated</HD>
                    <P>To further support our effort to ensure ubiquitous STIR/SHAKEN implementation and increase the number of calls that terminate with attestation information, we propose to: (1) prohibit voice service providers from intentionally routing calls to strip authentication information; (2) require that providers block unauthenticated SIP calls transmitted directly to them (except public safety calls); and (3) require that all intermediate providers authenticate any unauthenticated non-SIP calls they receive. We believe these requirements, in combination with the KYUP requirements we propose above, will serve to remove bad actor providers from the voice network, as well as reduce the incentives for providers to maintain non-IP networks, thereby further supporting the IP transition. We discuss each proposal in turn, as well as seek comment on other authentication-related issues.</P>
                    <P>
                        <E T="03">Prohibiting elective non-IP call routing.</E>
                         We propose to prohibit voice service providers from intentionally routing a call over a network that does not support the transmission of STIR/SHAKEN authentication information when it has the technical ability to route a call over a network that does support such transmission. In the 
                        <E T="03">Second Caller ID Authentication Order,</E>
                         85 FR 73360 (Nov. 17, 2020), the Commission declined to adopt one commenter's proposal to prohibit intermediate providers from passing a SIP call to a downstream provider in TDM when there is a downstream IP option available. As the Commission explained at the time, it did not wish to interfere with call routing decisions when the voice industry was in the early stages of STIR/SHAKEN deployment. In the six years since that order was adopted, STIR/SHAKEN has been widely deployed throughout the voice ecosystem, and yet the benefits of STIR/SHAKEN have been frustrated by the persistence of call routing over TDM networks—indeed, current data suggest the problem may be worsening. According to statistics provided by TransNexus, the percentage of calls terminating in the United States that are signed with STIR/SHAKEN dropped from 49% in October 2024 to 38% in September 2025. TransNexus attributes this downward trend, at least in part, to the routing of calls over non-IP segments along the call path. TransNexus argues that, if providers are choosing to route their calls over non-IP segments, this tactic would “enable such providers to claim compliance with the Commission's call authentication rules while remaining unaccountable for their calls within the STIR/SHAKEN ecosystem.” ACA International et al. also contend that “scam calls are deliberately routed through TDM interconnections for the purpose of stripping out STIR/SHAKEN information to reduce the chances that the calls will be blocked.”
                    </P>
                    <P>
                        We seek comment on this proposal. How easily can providers intentionally route calls over networks that do not support the transmission of authentication information? To what extent can they ensure that calls are routed over networks that support transmission of authentication information when available? What impact would such a prohibition have on providers' least-cost routing practices (where call routing is based on the lowest cost rather than on signaling protocol)? We believe that the benefits of preserving STIR/SHAKEN authentication information with a call outweigh any additional cost of selecting an IP route for the call, and we note that, in 2018, the NANC recommended that “all carriers that route calls between originating and terminating carriers, such as long-distance providers and least-cost routers, maintain the integrity of the required SHAKEN/STIR signaling.” We seek comment on these views. What percentage of calls are routed over networks that cannot support the transmission of authentication information due to least cost routing? Are there existing least cost routing arrangements that may prevent providers from routing calls over networks that support the transmission of authentication information? Do commenters support the inclusion of intent in this rule, or should we instead adopt a strict liability regime? What evidentiary findings would establish intent? By what metric should we consider that a provider has the technical ability to route a call over IP? Would such a rule risk incentivizing bad actor providers to cease interconnecting in IP altogether so that the only “available option” for routing a call is over a TDM interconnection point? If so, how could we deter this? Would downstream providers be able to determine when a bad actor is seeking to interconnect in TDM specifically to circumvent this rule, such as by using the KYUP measures we propose above? Should we place more direct obligations on downstream providers to ensure that the upstream providers with which they interconnect are not engaged in prohibited routing practices? If so, what obligations should we adopt? Rather than adopting this prohibition, should we instead require the use of a non-IP caller ID authentication mechanism, as explored in the 
                        <E T="03">Non-IP Caller ID Authentication NPRM,</E>
                         90 FR 25186 (Dec. 16, 2025)?
                    </P>
                    <P>
                        <E T="03">Blocking unauthenticated SIP calls.</E>
                         We propose to require that non-gateway intermediate providers and terminating providers block SIP calls that use NANP resources in the caller ID field transmitted directly to them without STIR/SHAKEN authentication information, except 911, 988, and other public safety calls. For clarity, we are not proposing that providers block calls transmitted to them from a non-IP network, such as TDM. We also limit the proposed requirement to non-gateway intermediate providers because gateway providers may receive unauthenticated SIP calls from foreign voice service providers and we do not propose that such calls should be blocked. We believe that some providers may not be fulfilling their obligation to authenticate SIP calls, potentially to obscure the identity of the originating provider and/or the caller. For instance, ZipDX notes that in “approximately 
                        <PRTPAGE P="42626"/>
                        65% of tracebacks, the originating provider is identified as having signed the call,” suggesting that the remaining 35% were unsigned. All voice service providers are required to have implemented STIR/SHAKEN in their IP networks, and if we adopt our proposal below that intermediate providers authenticate any unauthenticated calls they receive (namely, those received from non-IP networks), no providers should receive an unauthenticated SIP call unless the upstream provider is violating our rules, subject to a certain narrow technical and security exemption that we address herein. We believe that unauthenticated SIP calls are presumptively unlawful, and therefore that blocking is warranted. We seek comment on this view and additional evidence on the extent to which providers are not authenticating SIP calls they are transmitting. Apart from the circumstances that permit an intermediate provider to remove authentication information under our rules, are there any other legitimate reasons a lawful call on an IP network would not have authentication information? What is the scope of legitimate calls that may be blocked under this rule? Are there any technical limitations to identifying whether a call was transmitted in IP or blocking them when they are not authenticated? Would such a rule risk incentivizing bad actor providers to cease interconnecting in IP altogether so that they only transmit calls in non-IP? If so, how could we deter this? Is our proposal above to prohibit intentional non-IP call routing a necessary counterpart to this proposal in addressing this incentive issue? Should we instead require any provider that accepts an unsigned call to add to the call's identity header information about the voice service provider from which it received the call, such as the voice service provider's OCN, along with an indication of whether the call was received in TDM or IP? Is there a legal and policy basis for requiring non-gateway intermediate providers and terminating providers to block unauthenticated SIP calls that 
                        <E T="03">do not</E>
                         use NANP resources in the caller ID field?
                    </P>
                    <P>To facilitate this proposed blocking rule, we propose to modify our rule that allows intermediate providers to remove caller ID authentication information in certain circumstances to require that they reauthenticate any such calls if they will be transmitting the call to another provider in IP. Under our current rules, intermediate providers may strip such information: (1) where necessary for technical reasons to complete the call; and (2) where the intermediate provider reasonably believes the caller ID authentication information presents an imminent threat to its network security. By requiring them to reauthenticate the call, it will ensure that all SIP calls arrive at the terminating provider with authentication information. It will also prevent the calls from being blocked by the next downstream provider in the call path under our proposed blocking rule. Is such reauthentication technically feasible? We also seek comment on whether the two exceptions remain necessary. Are there actual instances where they remain necessary?</P>
                    <P>
                        <E T="03">Requiring non-gateway intermediate providers to authenticate non-SIP calls.</E>
                         We propose to require that all non-gateway intermediate providers authenticate non-SIP calls using NANP resources in the caller ID field that they receive and will exchange with another provider as a SIP call. As permitted by the Commission's third-party authentication rules, an intermediate provider could satisfy this proposed requirement through third-party authentication. We do not propose to apply this rule to gateway providers as they are already required to authenticate any unauthenticated calls they receive using U.S. NANP resources that they will exchange with another provider as a SIP call. While we propose above to require that non-gateway intermediate providers block any unauthenticated SIP calls using NANP resources in the caller ID field that they receive, they will still receive unauthenticated non-SIP calls, such as those sent from TDM networks. Under our current rules, the first intermediate provider in the call path must authenticate any unauthenticated calls they receive directly from an originating provider. Our rules technically require all intermediate providers to authenticate any unauthenticated caller ID information for the SIP calls they receive or, alternatively, cooperate with the industry traceback consortium and timely and fully respond to all traceback requests received from the Commission, law enforcement, and the industry traceback consortium. But in the 
                        <E T="03">Fourth Call Blocking Order,</E>
                         86 FR 17726 (April 6, 2021), the Commission required all providers in the path of a SIP call to respond fully and in a timely manner to traceback requests, so intermediate providers could automatically decline to authenticate caller ID information. In the 
                        <E T="03">Sixth Caller ID Authentication Order,</E>
                         the Commission established the requirement that the first intermediate provider in the path of an unauthenticated SIP call authenticate the call. We propose to modify that rule to place the authentication requirement on all intermediate providers and by narrowing it to non-SIP calls that they will not be blocking based on the proposed rule above. While the existing rule only requires authentication by the first intermediate provider, if the call transits another TDM network later in the call path, the authentication information would be stripped. We believe that requiring all non-gateway intermediate providers to authenticate any unauthenticated IP calls they receive will increase the number of calls that arrive at terminating providers with authentication information. Although authentication by intermediate providers will necessarily carry a C-level attestation (because the provider is not originating the call), we believe having these non-gateway intermediate provider attestations may help efforts to identify non-IP gaps in the voice network.
                    </P>
                    <P>
                        We seek comment on this proposal and analysis. What is the prevalence of unauthenticated calls transiting intermediate providers' networks due to non-IP networks? How often does an intermediate provider's authentication get stripped out by a later non-IP segment and then get passed to another intermediate provider? Will the intermediate provider attestations benefit call analytics and/or traceback efforts? Is there a legal and policy basis for requiring non-gateway intermediate providers to authenticate non-SIP calls that 
                        <E T="03">do not</E>
                         use NANP resources in the caller ID field? We acknowledge that adoption of this proposal would depart from the Commission's decision in the 
                        <E T="03">Sixth Caller ID Authentication Order</E>
                         to not extend the authentication requirement to all intermediate providers due to progress toward non-IP authentication solutions and the transition to IP interconnection and because of the burdens on intermediate providers. The Commission has a pending proceeding proposing to require that providers adopt non-IP caller ID authentication solutions, and has also been undertaking numerous efforts to promote providers completing their transition to all-IP. We now suspect that the burden on intermediate providers may be limited because many likely already have the capability to authenticate calls given that they could be the first one in the call path to receive an unauthenticated call. We also now believe that requiring authentication by intermediate providers will be beneficial while the IP 
                        <PRTPAGE P="42627"/>
                        transition is completed or providers adopt non-IP caller ID authentication solutions, and we note that the Commission resolved in the 
                        <E T="03">Sixth Caller ID Authentication Order</E>
                         to consider expanding a caller ID authentication requirement to all intermediate providers in the future, should such a step be warranted. Are these views accurate?
                    </P>
                    <P>
                        <E T="03">Other Authentication Issues.</E>
                         We seek comment on whether to require a voice service provider to populate the origination identifier (“origid”) field in a call's identity header with the provider's OCN, FRN, RMD number, or other standardized identifier to assist providers with identifying upstream providers generating unlawful calls or with traceback efforts. ATIS-1000088 recommends that the origid value “be a persistent and/or permanently assigned value at the selected source granularity.” If we require standardized use of the origid field, what level of granularity should we require? Would standardization of this field foreclose innovative uses? Could the Commission obligate downstream intermediate providers to cease accepting calls signed with a certain origid once it is discovered that a bad actor provider associated with that origid is the source of illegal robocalls?
                    </P>
                    <P>We also seek comment on whether we should take steps to address “instances where forwarded calls are sent without the proper SIP headers,” leading to improper call blocking and labeling by analytics systems. How prevalent is this issue and what, if anything, should the Commission do to resolve it?</P>
                    <HD SOURCE="HD2">D. Special Circumstances</HD>
                    <HD SOURCE="HD3">1. STIR/SHAKEN for TRS Providers</HD>
                    <P>
                        We seek comment on how our STIR/SHAKEN requirements apply to TRS providers in light of the changes we propose above, and what the impact of those requirements are on such providers. Specifically, we seek to understand how the requirements apply to providers of each form of TRS, given their distinct service configurations, including: TRS providers who do not have registered users, but receive calls to relay centers through consumers dialing 711 or a toll-free number (The two providers of TTY-based relay services, Speech-to-Speech relay services, and Captioned Telephone Services have agreements with state TRS programs to provide these services. The state TRS programs are each overseen by, or a part of, a state agency and each is certified with the Commission.); Video Relay Service (VRS) and internet Protocol Relay Service (IP Relay) providers that are required to assign telephone numbers to their registered users (VRS and IP Relay providers must be certified by the Commission to receive compensation for relay services. An individual must register with and provide a certification of eligibility to a provider in order to use relay services under the TRS program.); and internet Protocol Captioned Telephone Service (IP CTS) providers that may assign telephone numbers if they are also providing voice services to their registered users(IP CTS providers must also be certified by the Commission to receive compensation for relay services. An individual must register with and provide a certification of eligibility to a provider in order to use relay services under the TRS program. An IP CTS user will also go through the identity and address verification process in the TRS User Registration Database, once the database is ready.) Commenters representing these stakeholders responding to the 
                        <E T="03">Call Branding FNPRM</E>
                         and the 
                        <E T="03">Triennial Report Public Notice,</E>
                         90 FR 42578 (Sep. 3, 2025) have indicated that downstream providers have begun treating them as voice service providers with a STIR/SHAKEN implementation obligation, and are treating, or have threatened to treat, their calls as unsigned and lower their attestation levels if these providers do not implement STIR/SHAKEN. These practices by downstream providers, they say, disproportionally harm individuals with disabilities, whose calls would be viewed as untrustworthy by terminating providers and their customers.
                    </P>
                    <P>
                        Stakeholders for the various types of TRS variously assert that TRS providers are not voice service providers and that even if they were, they would be subject to the non-facilities-based provider exemption, cannot obtain SPC tokens, or should receive A-level attestations by default. We note that staff's review of RMD filings identified several providers of TRS, VRS, and IP CTS that claim the SPC token exception, asserting that they are not “telecommunications carriers” or a “provider of private telecommunications,” that they are not required to have an FCC Form 499-A on file with the FCC, or that they have not been assigned an OCN. However, all of these providers also indicate that they lack control over the network infrastructure necessary to implement STIR/SHAKEN or rely on technology that cannot initiate, maintain, carry, process, and terminate SIP calls (
                        <E T="03">i.e.,</E>
                         non-IP networks). We seek clarity, in the context of each specific form of TRS, on whether TRS providers are or are not voice service providers under the definitions we propose above. Do our proposed revised definitions above resolve this question for each form of TRS? If any TRS providers are voice service providers, would they be initiating or originating voice service providers, and what are the implications of each classification for a TRS provider? In what situations, if any, would routers that TRS providers use be considered “facilities” under our proposed definition, and should there be a categorical rule that some or all types of TRS providers qualify for the non-facilities-based provider exemption regardless of the definition of “facilities”? Would our proposal above to require voice service providers that serve end users directly to make attestation-level decisions regarding their end users' calls—and for originating providers to sign their calls using those attestation-level decisions—address the issue of TRS providers' calls not receiving an appropriate level of trust by downstream providers? Are there other issues presented if the entity providing voice connectivity to the TRS provider is itself a non-facilities-based voice service provider? If a TRS provider does not qualify for the exemption or we require an attestation mechanism that involves obtaining an SPC token, would such provider be able to obtain an SPC token from the Governance Authority? If not, should we establish an undue hardship extension for such providers? Or, should we require that the Governance Authority modify its policy so that they are able to obtain SPC tokens, and if so, how should the policy be modified to ensure such TRS providers can participate in the STIR/SHAKEN ecosystem without creating a loophole that bad actors could exploit? Are there any issues for these providers related to the costs of implementing STIR/SHAKEN? Should we simply mandate that calls from TRS providers be given an A-level attestation to ensure that calls from individuals with disabilities are treated as trustworthy? What are the practical and technical challenges, if any, with implementing such a requirement? Would such a requirement create a loophole that bad actors could easily exploit? What, if any, of these issues would be resolved by the IP transition, and should we simply continue our efforts to spur the transition?
                    </P>
                    <HD SOURCE="HD3">2. Addressing Foreign Calls With KYUP and STIR/SHAKEN Authentication</HD>
                    <P>
                        We seek comment on how our proposals would serve to deter illegal calls that enter the United States from 
                        <PRTPAGE P="42628"/>
                        abroad, and whether we should take any further actions related to KYUP and caller ID authentication in that regard.
                    </P>
                    <P>We believe the KYUP obligations we propose above will provide two mechanisms to identify foreign bad actor providers and foreign-originated calls. First, we believe that KYUP obligations will require gateway providers to scrutinize the foreign voice service providers from which they accept calls and require that they refuse or discontinue service to foreign voice service providers who are transmitting illegal calls. Second, we believe the KYUP obligations will require all voice service providers to scrutinize upstream providers that claim to be domestic providers to determine whether that is in fact the case. In particular, we believe the KYUP obligations will allow providers to identify foreign voice service providers that have attempted to establish nominal operations within the United States to avoid their calls being scrutinized as foreign-originated. Should we impose more specific obligations on providers to identify bad actor foreign providers or illegal foreign calls and stop them? Are there any KYUP obligations we propose above that we should not require providers to perform for foreign providers? Should we require gateway providers to adopt strict contract provisions with foreign providers that require the foreign providers to use meaningful KYUP and KYC requirements?</P>
                    <P>We also seek comment on how our proposals will advance or hamper ongoing efforts to achieve Cross Border Call Authentication (CBCA), and whether we should do more to support that effort. CBCA is an initiative that would purportedly “allow calls to be verified end-to-end in an all-IP traffic exchange environment, even if they originate in a country that has not yet deployed [STIR/]SHAKEN.” Would any of our proposals above hamper implementation of CBCA? Even if any would, given the broad array of stakeholders that have raised concerns about how STIR/SHAKEN is implemented in the United States, would that be outweighed by the benefits of enhancing STIR/SHAKEN implementation in the United States? Would maintaining the current standards to facilitate CBCA implementation serve to increase the risk that illegal calls will enter the United States from abroad, thereby exacerbating the problems that presently exist? Does the CBCA standard provide robust guardrails to prevent bad actors from using the mechanism to target United States consumers with foreign-originated illegal calls that will be authenticated as legal? What obligations will be placed on domestic providers to prevent misuse by foreign-based providers? Will the Commission and other United States enforcement entities have sufficient jurisdiction to address improper application of CBCA if it is implemented? Should we adopt rules applicable to domestic providers to facilitate CBCA while also protecting consumers from foreign-originated illegal calls? If so, what should those rules be? Will CBCA facilitate the use of tracebacks to identify foreign intermediate providers at each point in a call path and the foreign originating providers at the beginning of the call path, at least in the countries that use it?</P>
                    <P>We further seek comment on how foreign providers may be engaged in the United States STIR/SHAKEN ecosystem today. Are stakeholders, including the Governance Authority, taking adequate steps to prevent foreign providers from participating in the United States STIR/SHAKEN ecosystem? Should we take additional steps to ensure the Governance Authority does not grant SPC tokens to foreign providers? Are gateway providers accepting authentication information on foreign-originated calls and passing it unaltered to the next provider in the call path? If so, should we prohibit gateway providers from accepting authentication information from foreign voice service providers in the absence of CBCA?</P>
                    <HD SOURCE="HD3">3. Public Safety Safeguards</HD>
                    <P>
                        We seek comment on downstream impacts any of our proposals would have on 911 service and public safety, including Public Safety Answering Points (PSAPs), particularly as it relates to the transition to Next Generation 911 (NG911). As part of our efforts to expedite the deployment of modern, high-speed IP networks, we have recognized the importance of promoting a reliable and effective 911 system that protects consumers. We have also proposed measures related to the use of IP technology and the transition to IP for combatting illegal calls while remaining cognizant of protecting consumer access to emergency services. Today, 911 Authorities have requested delivery of 911 calls in IP-based SIP format covering nearly 1,700 PSAPs. Under Phase 1 of the FCC's NG911 transition rules, upon receipt of a 911 Authority's valid request, originating providers must, among other things, obtain and deliver 911 traffic to enable NG911 networks to transmit all 911 traffic to the destination PSAP. In addition, the originating provider must also complete connectivity testing to confirm that the 911 Authority receives 911 traffic in the IP-based SIP format requested by the 911 Authority. In an all-IP, NG911 environment, we anticipate our proposals herein will help minimize disruptions, such as spoofing, to PSAPs receiving SIP calls. In addition, our proposals should help PSAPs and emergency services that rely on SIP to place return calls to end users and consumers. We invite comment on how any of our proposals would be implemented in transitional 911 environments (
                        <E T="03">i.e.,</E>
                         an environment with mixed TDM/IP facilities) that include legacy gateways for converting IP calls. Since, in the 911 context, originating providers may have to convert IP calls to TDM as part of the NG911 transition, should we require providers to identify any TDM conversions that are necessary for delivering 911 service as part of the KYUP requirements? To the extent we establish exceptions to blocking requirements and other rules to prevent disruptions to 911 and other public safety calls, are there additional measures that we could apply to mitigate spoofing? For example, should we require providers to report suspicious 911 calls to the Commission and Governance Authority for investigation? Should 911 Authorities be allowed to report spoofing calls to the Commission and Governance Authority? What other measures should service providers, including 911 service providers, take to safeguard 911 and emergency communications in a mixed TDM/IP environment? Would requirements in this document lead to blocking 911 calls from Non-Service Initialized (NSI) callers? Commenters should also discuss any standards in development to mitigate spoofing to 911 and emergency communications.
                    </P>
                    <P>
                        We also seek comment on whether to amend the public safety exceptions in our call blocking and Robocall Mitigation Database rules to explicitly include calls made to emergency services other than 911, including calls to or from the 988 Suicide &amp; Crisis Lifeline (Lifeline). Our 988 rulemakings have established that the Lifeline is an “emergency network” under the Twenty-First Century Communications Video and Accessibility Act (CVAA). And, in discussing protections for emergency services, the TRACED Act and the TCPA, which provide authority for our RMD and call blocking rules, refer generally to “emergency public safety calls” and “emergency telephone line[s],” including, but not limited to, 911. However, in carving out exceptions for calls to emergency services, our RMD and call blocking rules refer 
                        <PRTPAGE P="42629"/>
                        exclusively to emergency calls to 911. Should we revise these rules to explicitly include calls to the 988 Lifeline? Likewise, should we clarify that calls from a 988 crisis center are included under the umbrella of calls from “government emergency numbers” that providers must make reasonable efforts to avoid blocking under these rules? Are such amendments necessary? Would they impose significant burdens on providers or the Lifeline—including affiliated entities such as the Veterans Crisis Line or local crisis centers? Would they reduce the risk of providers blocking lawful calls to 988 seeking lifesaving care? Alternatively, would they subject the Lifeline to increased levels of illegally spoofed robocalls, or other malicious calls, thereby reducing the resources available to legitimate callers? Beyond the 988 Lifeline, are there other emergency services that we should consider including in these public safety exceptions to our robocall blocking rules?
                    </P>
                    <HD SOURCE="HD2">E. Implementation Considerations</HD>
                    <HD SOURCE="HD3">1. Enforcement and Other Accountability Measures</HD>
                    <P>We propose to enhance base forfeiture amounts for violations of our existing and proposed KYUP and STIR/SHAKEN rules, which we believe will better encourage compliance and thereby enhance consumer protections against illegal calls. Specifically, we propose to adopt a $2,500 per call base forfeiture for calls resulting from a failure to follow KYUP requirements. Additionally, we propose to codify a base forfeiture amount of $1,000 per call for violations of the proposed rules concerning improper attestations and unauthenticated calls. We further propose to codify a $2,500 base forfeiture amount, on a continuing violation basis, for providers who have failed to implement STIR/SHAKEN and are not subject to any exemption.</P>
                    <P>
                        We seek comment on whether we should adopt or promote other measures to hold providers accountable to existing obligations and those we may adopt as proposed above. For instance, should we state that providers are violating our rules if they accept SIP calls from an upstream provider that does not have an SPC token? Should we encourage or require terminating providers to offer consumers tools to block calls or send them to voicemail based on the reputation of the originating provider? If we were to mandate the offering of such tools, should such mandate apply only to providers of a certain size (
                        <E T="03">e.g.,</E>
                         a million or more subscribers)? Additionally, we seek comment on whether we should explore preemption of state requirements in the field of caller ID authentication to prevent requirements that are inconsistent with the careful approaches we propose to adopt. Would this ensure a uniform foundation for federal and state enforcement activities?
                    </P>
                    <HD SOURCE="HD3">2. Reporting to the Commission and Governance Authority</HD>
                    <P>We propose to require that voice service providers report to the Commission's Enforcement Bureau and to the STIR/SHAKEN Governance Authority any providers they reasonably believe are or may be transmitting illegal calls or violating KYUP or authentication requirements, including improper attestations. We further propose that such reports include a summary of providers' findings and conclusions. We believe that such reporting will aid the Commission and the Governance Authority in their efforts to identify and take action against bad actor providers and the individuals and entities that are behind them. We seek comment on whether we should establish a new mechanism for providers to submit reports to the Commission or use an existing mechanism, such as the Enforcement Bureau's Private Entity Robocall and Spoofing Portal. We also seek comment on how providers will report to the Governance Authority. Do we need to adopt confidentiality measures for reporting? Would any concerns arise from such reporting related to sensitive personal or business information? We also seek comment on whether we should set specific parameters of what the reports should contain or whether we should delegate authority to the Bureau to develop the parameters in consultation with the Enforcement Bureau.</P>
                    <HD SOURCE="HD3">3. Bringing Clarity to Caller ID Authentication Rules and Obligations</HD>
                    <P>In this section we propose and seek comment on steps to bring clarity to the Commission's caller ID authentication rules.</P>
                    <P>
                        <E T="03">Streamlining caller ID authentication rules.</E>
                         We propose to take a comprehensive review of the Commission's existing STIR/SHAKEN caller ID authentication rules in §§ 64.6300 through 64.6308. In doing so, we endeavor to simplify the rules to remove unnecessary redundancy, ensure consistency, and increase clarity, with the goal of enhancing providers' ability to understand their obligations. We also believe this will enhance the Commission's ability to administer the rules as we enforce them and make future updates, including the updates we propose above. By this proposal, we intend to leave unaltered any obligations presently applicable to voice service providers, except to the extent we incorporate proposed modifications above and the one proposed departure below. We note that there are certain minor proposed changes that reflect codification of requirements that were stated in prior Commission orders, such as the requirement that providers implement the STIR/SHAKEN framework in accordance with the STIR/SHAKEN standards. As such, we encourage commenters to closely review the proposed rules in Appendix A to ensure the streamlined rules reflect the provider obligations set out in prior Commission actions and proposed above. Of particular note, we propose to remove the subparagraph numbers for the definitions in § 64.6300, which is consistent with the Federal Register Document Drafting Handbook recommendation, and will allow us to add future definitions in alphabetical order without causing confusion related to cross-references in the Commission's rules and when rules are cited in Commission items over time. The one departure concerns the scope of the robocall mitigation program obligation for gateway providers, which is currently limited to calls using United States NANP resources in the caller ID field. We do not believe there is any statutory or policy requirement for limiting gateway providers' obligation to mitigate illegal calls to only calls they receive that use United States NANP resources in the caller ID field, and further believe that gateway providers should attempt to mitigate any illegal calls they receive. As such, we propose to modify gateway providers' obligation to require that their robocall mitigation programs apply to all calls they carry and process.
                    </P>
                    <P>
                        <E T="03">Definitions related to the Governance Authority.</E>
                         To promote better clarity in our rules, we propose to define “certificate,” “Certification Authority,” and “Policy Administrator” for the purposes of our caller ID authentication rules. Specifically, we propose to define “certificate” as a digital data object obtained from a Certification Authority which is used by a voice service provider to sign and verify caller identification information consistent with the STIR/SHAKEN authentication framework. We propose to define “Certification Authority” as an entity that issues certificates and vouches for the binding between the data items in a certificate. Finally, we propose to define 
                        <PRTPAGE P="42630"/>
                        “Policy Administrator” as a STIR/SHAKEN governance body that applies rules set by the Governance Authority, confirms that Certification Authorities are authorized to issue certificates, and confirms that voice service providers are authorized to request and receive certificates. We also propose to amend the definition of SPC token to clarify that the SPC token allows a voice service provider to obtain a certificate from a Certification Authority. It is common in industry parlance to describe a voice service provider as signing caller ID authentication information with the provider's SPC token. We understand this usage to be an elision, as it is the certificate which is most directly used to sign calls. As our rules properly obligate voice service providers to sign calls using the certificate, amending the definition of SPC token will ensure consistency with those rules. We define these terms consistent with ATIS usage to avoid unnecessary industry confusion. We seek comment on these definitions.
                    </P>
                    <HD SOURCE="HD3">4. Effective Date</HD>
                    <P>
                        We propose that the proposed rules herein become effective the later of 12 months after 
                        <E T="04">Federal Register</E>
                         publication of a Report and Order adopting the rules or 30 days after approval by the Office of Management and Budget (OMB) for rules that contain new or modified information collections subject to review under the Paperwork Reduction Act (PRA). We seek comment on this proposal. Should we adopt different effective dates for different rules or for different types of providers, such as small providers?
                    </P>
                    <HD SOURCE="HD2">F. Legal Authority</HD>
                    <P>
                        We propose to adopt the above proposals pursuant to our authority in Sections 201(b), 202(a), and 251(e) of the Act, the Truth in Caller ID Act, the TRACED Act, and, where appropriate, our ancillary authority, consistent with the authority we have invoked to adopt analogous rules in our 
                        <E T="03">Caller ID Authentication</E>
                         and 
                        <E T="03">Call Blocking Orders.</E>
                         We seek comment on these proposals.
                    </P>
                    <P>
                        <E T="03">Proposed KYUP Requirements.</E>
                         We intend to rely on Sections 201(b), 202(a), and 251(e) of the Act, as well as the Truth in Caller ID Act, as support for the proposed KYUP and related call blocking requirements because they are aimed at reducing spoofing and curbing the use of NANP numbers for unlawful purposes. Sections 201(b) and 202(a) provide the Commission with “broad authority to adopt rules governing just and reasonable practices of common carriers.” The Commission has previously concluded that the existing KYC and KYUP requirements are “clearly within the scope of our Section 201(b) and 202(a) authority” with respect to common carriers. In addition, the Commission has found that Section 251(e) and the Truth in Caller ID Act provide the basis to prescribe rules to prevent the unlawful spoofing of caller ID and abuse of NANP resources by all voice service providers, which for purposes of our call blocking, KYC, and KYUP rules includes interconnected VoIP providers. Specifically, the Commission has found that our “Section 251(e) numbering authority provides separate jurisdiction to prevent the fraudulent abuse of North American Numbering Plan (NANP) resources,” which “particularly applies where callers spoof caller ID for fraudulent purposes and therefore exploit numbering resources, regardless of whether the voice service provider is a common carrier.” Similarly, the Commission has found that “the Truth in Caller ID Act grants us authority to prescribe rules to make unlawful the spoofing of caller ID information with the intent to defraud, cause harm, or wrongfully obtain something of value.” We believe these same statutory provisions support the enhanced KYUP and blocking requirements we propose here and seek comment on this view. Are there additional sources of authority we should consider?
                    </P>
                    <P>We also intend to rely on authority in Section 4 of the TRACED Act, which directs the Commission to, among other things, establish “when a provider of voice service may block a voice call based in whole or in part on information provided by the call authentication frameworks.” This provision lends support to the KYUP proposal because it may require providers to evaluate various aspects of an upstream providers' STIR/SHAKEN implementation when determining whether to accept calls from an upstream provider. Additionally, pursuant to Section 7 of the TRACED Act, the Commission initiated a rulemaking to “help protect a subscriber from receiving unwanted calls or text messages from a caller using an unauthenticated number.” We believe the KYUP proposals and associated call blocking requirement would have the effect of protecting consumers from unwanted calls from unauthenticated numbers. We seek comment on this analysis.</P>
                    <P>
                        <E T="03">Proposed caller ID authentication requirements.</E>
                         We intend to rely on Section 4 of the TRACED Act for the STIR/SHAKEN proposals herein. Congress expressly directed the Commission to require voice service providers to implement the STIR/SHAKEN caller ID authentication framework in Section 4 of the TRACED Act. Consistent with the Commission's prior call blocking and caller ID authentication orders, we find that Sections 201(b) and 201(a) of the Act, and the Commission's ancillary authority in Section 4(i) of the Act, provide us with additional sources of authority to adopt these robocall mitigation requirements. We believe that adopting the proposed requirements above, which are designed to ensure the ubiquitous and consistent implementation of STIR/SHAKEN, fits squarely within our authority to require that voice service providers implement STIR/SHAKEN. Assuming we adopt our proposal to read the TRACED Act's “voice service” definition to include intermediate providers consistent with the RAY BAUM'S Act and § 64.1600(r) of the Commission's rules, we believe the TRACED Act gives us authority to apply these requirements to all originating, intermediate, and terminating providers. We also intend to rely on the TRACED Act for authority to adopt our proposals related to the STIR/SHAKEN Governance Authority. These rules will better ensure that providers are held accountable for properly implementing STIR/SHAKEN, thereby enhancing the trust and integrity upon which STIR/SHAKEN relies. We seek comment on this analysis.
                    </P>
                    <P>We also intend to rely on Section 251(e) of the Act and the Truth in Caller ID Act, which we believe each provide the Commission with independent authority to exercise the proposed oversight of the Governance Authority, require providers to adopt the enhanced attestation requirements using the STIR/SHAKEN framework, clarify the definitions related to application of the STIR/SHAKEN requirements, and address the remaining loopholes to STIR/SHAKEN implementation. The Commission has consistently relied on these provisions to establish requirements related to STIR/SHAKEN caller ID authentication as a means of preventing the fraudulent abuse of NANP resources as directed in Section 251(e) and as directed in the Truth in Caller ID Act to deter unlawful spoofing. We seek comment on these views.</P>
                    <P>
                        <E T="03">Ancillary authority.</E>
                         While we propose to conclude that our direct sources of authority provide an ample basis to adopt our proposed rules on voice service providers, we intend, as we have with our prior rulemakings addressing illegal calls, to rely on our ancillary authority in Section 4(i), which provides an independent basis to adopt 
                        <PRTPAGE P="42631"/>
                        rules with respect to voice service providers that have not been classified as common carriers. We seek comment on this view. The Commission has previously relied on its ancillary authority in Section 4(i) to apply the existing KYC, KYUP, and call blocking requirements to such providers, finding “that it is essential that the rules apply to all voice service providers.” We thus likewise believe that the proposed KYUP and call blocking requirements are “reasonably ancillary to the Commission's effective performance of its . . . responsibilities.” The Commission may exercise ancillary jurisdiction when two conditions are satisfied: (1) the Commission's general jurisdictional grant under Title I of the Act covers the regulated subject; and (2) the regulations are reasonably ancillary to the Commission's effective performance of its statutorily mandated responsibilities. Specifically, we believe the proposals satisfy the first prong because voice service providers are interconnected with the public switched telephone network, and exchanging IP calls clearly constitutes “communication by wire or radio” under Section 2(a) of the Act. We also believe the proposed requirements are reasonably ancillary to our exercise of authority under Sections 201(b) and 202(a), as we do not believe we could ensure that voice service providers that are classified as common carriers comply with obligations to address illegal calls if the same rules did not apply to voice service providers that are not classified as common carriers, and the inability of common carriers to comply with obligations could create a gap that bad actor providers could exploit. Additionally, we believe the proposals are reasonably ancillary to our authority in 251(e) and the Truth in Caller ID Act to combat spoofing and our authority in the TRACED Act to ensure mitigation and blocking of illegal calls using authentication information. We seek comment on this analysis.
                    </P>
                    <P>
                        <E T="03">Indirect effect on foreign voice service providers.</E>
                         We propose to conclude that, to the extent any of the rules we seek to adopt today have an effect on foreign voice service providers, that effect is only indirect and therefore consistent with the Commission's authority. In the 
                        <E T="03">Second Caller ID Authentication Order,</E>
                         the Commission acknowledged its rules would have an indirect effect on foreign providers but concluded that it was permissible under past Commission and court precedent. This includes the authority, pursuant to Section 201, for the Commission to require a domestic provider to modify its contracts with a foreign provider with respect to “foreign communication” to ensure that the charges and practices are “just and reasonable.” We propose to conclude that the proposed rules do not constitute the exercise of jurisdiction over foreign providers. We seek comment on this and on whether any of our proposed rules exceed the scope of our jurisdiction over foreign communications that enter the United States. We also seek comment on whether any of our proposed rules would be contrary to any of our international treaty obligations, contrary to other international laws and rules, or would create a risk of foreign retaliation.
                    </P>
                    <HD SOURCE="HD2">G. Cost-Benefit Analysis</HD>
                    <P>We seek comment on the overall costs and benefits of our proposals above and whether the benefits will outweigh the costs.</P>
                    <P>Consumers continue to be victims of significant fraud, and a substantial amount of the fraud is perpetrated through illegal calls. According to the most recent Federal Trade Commission Consumer Sentinel Network Data Book, 19% of reported fraud was due to phone calls and the median loss to individuals of such fraud was $1500 in 2024 for a total of $948M that year. Hiya's February 2026 State of the Call Report shows that consumers receive an average of seven unwanted calls every week with 15% of respondents saying they lost money to a phone scam in the last year, resulting in an average individual loss of $682 from phone scams in the United States. We believe that our proposals above will have a meaningful impact on reducing illegal calls, therefore substantially reducing the harms to consumers that result from these calls. In the long term, we believe more effective KYUP and caller ID authentication will increase trust in the nation's voice networks, yielding positive spillover benefits such as greater consumer willingness to answer legitimate calls, more effective communication between enterprises and their customers, and improved performance of emergency and public-safety calling systems. We seek comment on these views. What portion of providers already follow robust KYUP or STIR/SHAKEN practices, and therefore, to what extent will the benefits be incremental for customers of already-compliant providers? How will increased trust in authenticated voice communications manifest in measurable market or consumer outcomes? We also invite comment on appropriate methods to measure these benefits. How will these rules impact illegal calls? How should the Commission quantify the benefits or estimate the reduction in illegal calls? What data can the Commission use to measure these benefits?</P>
                    <P>We believe that the costs of our proposal will be minimal for providers that already take their KYUP and STIR/SHAKEN obligations seriously, as many of the proposals are designed to codify practices that providers should already be following to meet their obligations. We seek comment on this view. To what extent will the costs differ for different types of providers? What are the costs, and their impact, on small providers specifically? How may we mitigate such costs, if indeed there are any? Do other commenters agree with this assessment? Because our proposals are necessarily aimed at reducing the number of illegal calls that transverse the voice network, we recognize that providers may lose revenue if call volumes shrink. However, we believe these losses will be made up over time by increased call volumes resulting from the restoration of trust by consumers and businesses in voice communications. We seek comment on this assessment.</P>
                    <HD SOURCE="HD1">II. Regulatory Flexibility Analysis Initial Regulatory Flexibility Analysis</HD>
                    <P>
                        As required by the Regulatory Flexibility Act of 1980, as amended (RFA), the Federal Communications Commission (Commission) has prepared this Initial Regulatory Flexibility Analysis (IRFA) of the policies and rules proposed in the 
                        <E T="03">Further Notice of Proposed Rulemaking</E>
                         (
                        <E T="03">FNPRM</E>
                        ) assessing the possible significant economic impact on a substantial number of small entities. The Commission requests written public comments on this IRFA. Comments must be identified as responses to the IRFA and must be filed by the deadlines for comments specified on the first page of the 
                        <E T="03">FNPRM.</E>
                         The Commission will send a copy of the 
                        <E T="03">FNPRM,</E>
                         including this IRFA, to the Chief Counsel for the Small Business Administration (SBA) Office of Advocacy. In addition, the 
                        <E T="03">FNPRM</E>
                         and IRFA (or summaries thereof) will be published in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <HD SOURCE="HD2">A. Need for, and Objectives of, the Proposed Rules</HD>
                    <P>
                        The Commission has adopted a number of tools aimed at stopping unlawful and fraudulent calls, but these tools rely on proper implementation by responsible providers in the ecosystem. In furtherance of the Commission's mission to bring consumers meaningful relief from illegal calls and restore trust in voice communications, the 
                        <E T="03">FNPRM</E>
                         proposes measures to ensure all voice 
                        <PRTPAGE P="42632"/>
                        service providers are fulfilling their obligations to protect consumers from illegal calls through their implementation of the STIR/SHAKEN authentication framework. The STIR/SHAKEN framework, which is designed to deter number spoofing and supports other tools to combat illegal calls, is built on an expectation that providers will properly authenticate calls. Available evidence suggests that some providers have not implemented the framework consistently. We propose measures to address implementation issues, and thereby enhance STIR/SHAKEN, by preventing providers from transmitting calls when they fail to properly implement the framework, ensuring providers properly attest calls using the framework, and closing loopholes that are preventing ubiquitous and consistent deployment of the framework in providers' IP networks. Specifically, we: (1) propose that providers follow baseline measures to fulfill their obligation to know their upstream providers and that the STIR/SHAKEN Governance Authority improve its policies for authorizing providers to authenticate calls using the framework; (2) propose to require that providers follow know-your-customer (KYC) and know-your-upstream-provider (KYUP) requirements when making attestation-level decisions and prohibit improper attestations; (3) propose to close implementation loopholes by clarifying definitions, repealing an implementation exemption, requiring voice service providers closest to end users to authenticate calls, and implementing measures to increase the number of calls that arrive at terminating providers with caller ID authentication information; (4) seek comment on how these and other measures will address illegal foreign-originated calls; (5) propose and seek comment on how to hold providers accountable to these proposed requirements and any existing requirements; and (6) propose steps to ease providers' compliance with the Commission's caller ID authentication rules and improve their administrability.
                    </P>
                    <HD SOURCE="HD2">B. Legal Basis</HD>
                    <P>The proposed action is authorized pursuant to Sections 4(i), 4(j), 201, 202, 217, 227, 227b, 251(e), 303(r), 403, 501, 502, and 503 of the Communications Act of 1934, as amended, 47 U.S.C. 154(i), 154(j), 201, 202, 217, 227, 227b, 251(e), 303(r), 403, 501, 502, and 503.</P>
                    <HD SOURCE="HD2">C. Description and Estimate of the Number of Small Entities to Which the Proposed Rules Will Apply</HD>
                    <P>The RFA directs agencies to provide a description of and, where feasible, an estimate of the number of small entities that may be affected by the proposed rules, if adopted. The RFA generally defines the term “small entity” as having the same meaning as the terms “small business,” “small organization,” and “small governmental jurisdiction.” In addition, the term “small business” has the same meaning as the term “small business concern” under the Small Business Act. A “small business concern” is one which: (1) is independently owned and operated; (2) is not dominant in its field of operation; and (3) satisfies any additional criteria established by the SBA. The SBA establishes small business size standards that agencies are required to use when promulgating regulations relating to small businesses; agencies may establish alternative size standards for use in such programs, but must consult and obtain approval from SBA before doing so.</P>
                    <P>Our actions, over time, may affect small entities that are not easily categorized at present. We therefore describe three broad groups of small entities that could be directly affected by our actions. 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 34.75 million businesses. Next, “small organizations” are not-for-profit enterprises that are independently owned and operated and not dominant in their field. While we do not have data regarding the number of non-profits that meet that criteria, over 99 percent of nonprofits have fewer than 500 employees. Finally, “small governmental jurisdictions” are defined as cities, counties, towns, townships, villages, school districts, or special districts with populations of less than fifty thousand. Based on the 2022 U.S. Census of Governments data, we estimate that at least 48,724 out of 90,835 local government jurisdictions have a population of less than 50,000.</P>
                    <P>
                        The rules proposed in the 
                        <E T="03">FNPRM</E>
                         will apply to small entities in the industries identified in the chart below by their six-digit North American Industry Classification System (NAICS) codes and corresponding SBA size standard. Where available, we also provide additional information regarding the number of potentially affected entities in the industries identified below.
                    </P>
                    <GPOTABLE COLS="6" OPTS="L2,nj,i1" CDEF="s50,10,xs72,11,11,12">
                        <TTITLE>Table 1—2022 U.S. Census Bureau Data by NAICS Code</TTITLE>
                        <BOXHD>
                            <CHED H="1">
                                Regulated industry
                                <LI>(footnotes specify potentially affected entities within a </LI>
                                <LI>regulated industry where applicable)</LI>
                            </CHED>
                            <CHED H="1">NAICS code</CHED>
                            <CHED H="1">SBA size standard</CHED>
                            <CHED H="1">Total firms</CHED>
                            <CHED H="1">
                                Total
                                <LI>small firms</LI>
                            </CHED>
                            <CHED H="1">% Small firms</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Wired Telecommunications Carriers</ENT>
                            <ENT>517111</ENT>
                            <ENT>1,500 employees</ENT>
                            <ENT>3,403</ENT>
                            <ENT>3,027</ENT>
                            <ENT>88.95</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Wireless Telecommunications Carriers (except Satellite)</ENT>
                            <ENT>517112</ENT>
                            <ENT>1,500 employees</ENT>
                            <ENT>1,184</ENT>
                            <ENT>1,081</ENT>
                            <ENT>91.30</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Telecommunications Resellers</ENT>
                            <ENT>517121</ENT>
                            <ENT>1,500 employees</ENT>
                            <ENT>955</ENT>
                            <ENT>847</ENT>
                            <ENT>88.69</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Satellite Telecommunications</ENT>
                            <ENT>517410</ENT>
                            <ENT>$44 million</ENT>
                            <ENT>332</ENT>
                            <ENT>195</ENT>
                            <ENT>58.73</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">All Other Telecommunications</ENT>
                            <ENT>517810</ENT>
                            <ENT>$40 million</ENT>
                            <ENT>1,673</ENT>
                            <ENT>1,007</ENT>
                            <ENT>60.19</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s100,15,11,8">
                        <TTITLE>Table 2—Telecommunications Service Provider Data</TTITLE>
                        <BOXHD>
                            <CHED H="1">
                                2024 Universal service monitoring report telecommunications service provider data
                                <LI>(data as of December 2023)</LI>
                            </CHED>
                            <CHED H="2">Affected entity</CHED>
                            <CHED H="1">
                                SBA size standard
                                <LI>(1500 employees)</LI>
                            </CHED>
                            <CHED H="2">Total Number FCC form 499A filers</CHED>
                            <CHED H="2">Small firms</CHED>
                            <CHED H="2">% Small entities</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Competitive Local Exchange Carriers (CLECs)</ENT>
                            <ENT>3,729</ENT>
                            <ENT>3,576</ENT>
                            <ENT>95.90</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Incumbent Local Exchange Carriers (Incumbent LECs)</ENT>
                            <ENT>1,175</ENT>
                            <ENT>917</ENT>
                            <ENT>78.04</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Interexchange Carriers (IXCs)</ENT>
                            <ENT>113</ENT>
                            <ENT>95</ENT>
                            <ENT>84.07</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Local Exchange Carriers (LECs)</ENT>
                            <ENT>4,904</ENT>
                            <ENT>4,493</ENT>
                            <ENT>91.62</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="42633"/>
                            <ENT I="01">Local Resellers</ENT>
                            <ENT>222</ENT>
                            <ENT>217</ENT>
                            <ENT>97.75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Toll Resellers</ENT>
                            <ENT>411</ENT>
                            <ENT>398</ENT>
                            <ENT>96.84</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Telecommunications Resellers</ENT>
                            <ENT>633</ENT>
                            <ENT>615</ENT>
                            <ENT>97.16</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Wired Telecommunications Carriers</ENT>
                            <ENT>4,682</ENT>
                            <ENT>4,276</ENT>
                            <ENT>91.33</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Wireless Telecommunications Carriers (except Satellite)</ENT>
                            <ENT>585</ENT>
                            <ENT>498</ENT>
                            <ENT>85.13</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Wireless Telephony</ENT>
                            <ENT>326</ENT>
                            <ENT>247</ENT>
                            <ENT>75.77</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,r50,8,8,9">
                        <TTITLE>Table 3—Cable Entities Data</TTITLE>
                        <BOXHD>
                            <CHED H="1">Cable entities</CHED>
                            <CHED H="1">Size standard</CHED>
                            <CHED H="1">Total firms</CHED>
                            <CHED H="1">Small firms</CHED>
                            <CHED H="1">
                                % Small firms in
                                <LI>industry</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Cable System Operators (Telecom Act Standard) Small Cable Operator</ENT>
                            <ENT>Serves fewer than 498,000 subscribers, either directly or through affiliates</ENT>
                            <ENT>530</ENT>
                            <ENT>524</ENT>
                            <ENT>98.87</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD2">D. Description of Economic Impact and Projected Reporting, Recordkeeping, and Other Compliance Requirements for Small Entities</HD>
                    <P>The RFA directs agencies to describe the economic impact of proposed rules on small entities, as well as projected reporting, recordkeeping, and other compliance requirements, including an estimate of the classes of small entities which will be subject to the requirements and the type of professional skills necessary for preparation of the report or record.</P>
                    <P>
                        The 
                        <E T="03">FNPRM</E>
                         proposes measures that may involve new or additional compliance and recordkeeping requirements for small and other providers. Specifically, we propose to require that providers adopt specific measures to fulfill their existing KYUP obligations, including information collection, compliance review, information verification, monitoring, and responsive action measures. Upon the effective date of the rules, providers would be required to comply with these obligations with respect to new and renewing upstream providers, and would have an additional 6 months after the effective date of the rules to complete the KYUP information collection, compliance review, and information verification requirements for existing upstream providers. We further propose that providers retain the information they collect in connection with this requirement for four years and that they report to the Commission and STIR/SHAKEN Governance Authority any upstream provider they believe may be using their network or services to transmit illegal calls. We propose requiring providers use KYC and KYUP information to attest the calls they authenticate using the STIR/SHAKEN framework, and prohibit them from improperly authenticating calls. Additionally, we propose to require that all intermediate providers authenticate any unauthenticated SIP calls they receive, which is a capability that most intermediate providers should already have; propose to prohibit providers from originating or routing calls over non-IP networks with the intent thereby to strip caller ID authentication information; and propose to require that providers block unauthenticated SIP calls.
                    </P>
                    <P>
                        In the 
                        <E T="03">FNPRM,</E>
                         we seek comment on the costs and benefits of its proposals and inquiries, with specific regard to any potential compliance costs and burdens on small providers, including costs associated with collecting additional information, increasing monitoring, data retention, independent audits, or other operational costs that may result from these proposals. We believe some of these measures will have an economic impact on certain providers by reducing their revenue as result of the reduction in the number of unlawful calls that transverse the voice network, but that those costs may be made up by legitimate callers who regain trust in the voice network. We do not believe the KYUP requirements costs will be unreasonably burdensome for most small providers that are good actors who likely collect some of this information as part of their existing obligations. We believe that small providers in most cases either serve end users directly, and therefore will not have to perform the KYUP requirements, or interconnect directly with large providers that are easily able to demonstrate their legitimacy. The proposed measures are largely geared toward clarifying and enhancing the compliance expectations that providers already have under existing rules, which should minimize the costs and burdens on providers that have already implemented existing requirements properly or meaningfully. We believe that certain KYUP requirements will only apply to small and other providers that choose to enter into certain business relationships and that the burden is reasonable relative to the potential benefits in deterring illegal calls. We also propose to codify a base forfeiture amounts of $2,500 per call for calls resulting from a failure to follow KYUP requirements, $1,000 on a per call basis for violations of rules involving improper call attestations and an unauthenticated calls; and $2,500, on a continuing violation basis, for providers who have failed to implement STIR/SHAKEN and are not subject to any exemption. Small providers that have not already implemented adequate measures to know their upstream providers, or who need to develop procedures for retaining and reporting such information, may need to hire professionals, such as consultants, attorneys, or third parties to comply with these requirements. To the extent the reduction of illegal calls has an impact on providers, we believe these losses will be made up by increased trust and use of the voice network.
                    </P>
                    <P>
                        With regard to the STIR/SHAKEN implementation exemptions, we propose to repeal the undue hardship exemption for inability to obtain SPC tokens and seek comment on whether to repeal the exemption for small 
                        <PRTPAGE P="42634"/>
                        providers that originate calls via satellite using NANP numbers as well as on potential hardship exemptions. We believe all voice providers are able to obtain SPC tokens without undue hardship, and propose to repeal the extension for providers to obtain this token. We seek comment on whether undue hardship extensions should be granted for telecommunications relay service (TRS) providers if they satisfy the definition of “voice service provider.”
                    </P>
                    <P>We believe that the burden on intermediate providers authenticating calls will be minimal because most of these providers should already have the ability to authenticate calls. We also believe our proposal to prohibit intentional stripping of authentication information should not affect lawful providers. Additionally, we believe providers should already have the ability to block unauthenticated calls, as they are already required to block other calls under certain circumstances.</P>
                    <HD SOURCE="HD2">E. Discussion of Significant Alternatives Considered That Minimize the Significant Economic Impact on Small Entities</HD>
                    <P>The RFA directs agencies to provide a description of any significant alternatives to the proposed rules that would accomplish the stated objectives of applicable statutes, and minimize any significant economic impact on small entities. The discussion is required to include alternatives such as: “(1) the establishment of differing compliance or reporting requirements or timetables that take into account the resources available to small entities; (2) the clarification, consolidation, or simplification of compliance and reporting requirements under the rule for such small entities; (3) the use of performance rather than design standards; and (4) an exemption from coverage of the rule, or any part thereof, for such small entities.”</P>
                    <P>
                        We seek comment in the 
                        <E T="03">FNPRM</E>
                         on alternatives that may accomplish the Commission's objectives of stopping unlawful and fraudulent calls, while potentially minimizing the economic impact on small providers. Specifically, we seek comment on whether we should reduce the KYUP requirements, or whether there are alternatives to the proposed information collection, compliance review, information verification, and monitoring obligations that would allow small providers flexibility to identify bad actors. This includes whether to direct providers to adopt KYUP best practices based on existing resources, or give them a safe harbor for such adoption, instead of requiring them to adopt detailed obligations that small and other providers must follow. We also seek comment on whether we should allow for the use of third-party KYUP services, and if so, whether they would help reduce compliance burdens for small providers. Small entities are encouraged to bring to the Commission's attention any specific concerns they may have with the proposals detailed in the 
                        <E T="03">FNPRM</E>
                         and outline any additional alternatives that would accomplish the objectives of this proceeding.
                    </P>
                    <HD SOURCE="HD2">F. Federal Rules That May Duplicate, Overlap, or Conflict With the Proposed Rules</HD>
                    <P>None.</P>
                    <HD SOURCE="HD1">III. Ordering Clauses</HD>
                    <P>
                        Accordingly, pursuant to sections 4(i), 4(j), 201, 202, 217, 227, 251(e), 303(r), 403, 501, 502, and 503 of the Communications Act of 1934, as amended, 47 U.S.C. 154(i), 154(j), 201, 202, 217, 227, 251(e), 303(r), 403, 501, 502, and 503, and section 4 of the 
                        <E T="03">traced</E>
                         Act, 47 U.S.C. 227b, this 
                        <E T="03">Notice of Proposed Rulemaking is adopted.</E>
                         Pursuant to Executive Order 14215, 90 FR 10447 (Feb. 24, 2025), this regulatory action has been determined to be not significant under Executive Order 12866, 58 FR 51735 (Oct. 4, 1993).
                    </P>
                    <P>
                        <E T="03">It is further ordered</E>
                         that the Commission's Office of the Secretary, 
                        <E T="03">shall send</E>
                         a copy of this 
                        <E T="03">Notice of Proposed Rulemaking,</E>
                         including the Initial Regulatory Flexibility Analysis, to the Chief Counsel for the Small Business Administration (SBA) Office of Advocacy.
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 47 CFR Parts 1 and 64</HD>
                        <P>Administrative practice and procedure, Carrier equipment, Communications common carriers, Customer premises equipment, Penalties, Reporting and recordkeeping requirements, Telecommunications, Telephone. </P>
                    </LSTSUB>
                    <SIG>
                        <FP>Federal Communications Commission.</FP>
                        <NAME>Marlene Dortch,</NAME>
                        <TITLE>Secretary.</TITLE>
                    </SIG>
                    <HD SOURCE="HD1">Proposed Rules</HD>
                    <P>For the reasons discussed in the preamble, the Federal Communications Commission proposes to amend 47 CFR parts 1 and 64 as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 1—PRACTICE AND PROCEDURE</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 1 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>47 U.S.C. chs. 2, 5, 9, 13; 28 U.S.C. 2461 note; 47 U.S.C. 1754, unless otherwise noted.</P>
                    </AUTH>
                    <AMDPAR>2. Amend § 1.80 by revising table1 in paragraph (b)(11) to read as follows:</AMDPAR>
                    <STARS/>
                    <P>(b) * * *</P>
                    <P>(11) * * *</P>
                    <GPOTABLE COLS="2" OPTS="L2,nj,i1" CDEF="s150,10">
                        <TTITLE>
                            Table 1 to Paragraph 
                            <E T="01">(b)(11)</E>
                            —Base Amounts for Section 503 Forfeitures
                        </TTITLE>
                        <BOXHD>
                            <CHED H="1">Forfeitures</CHED>
                            <CHED H="1">
                                Violation
                                <LI>amount</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Misrepresentation/lack of candor</ENT>
                            <ENT>(1)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Failure to file required DODC required forms, and/or filing materially inaccurate or incomplete DODC information</ENT>
                            <ENT>$15,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Construction and/or operation without an instrument of authorization for the service</ENT>
                            <ENT>10,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Failure to comply with prescribed lighting and/or marking</ENT>
                            <ENT>10,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Violation of public file rules</ENT>
                            <ENT>10,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Submitting inaccurate or false information to the Robocall Mitigation Database (Continuing violation until cured)</ENT>
                            <ENT>10,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Violation of political rules: Reasonable access, lowest unit charge, equal opportunity, and discrimination</ENT>
                            <ENT>9,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unauthorized substantial transfer of control</ENT>
                            <ENT>8,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Violation of children's television commercialization or programming requirements</ENT>
                            <ENT>8,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Violations of rules relating to distress and safety frequencies</ENT>
                            <ENT>8,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">False distress communications</ENT>
                            <ENT>8,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">EAS equipment not installed or operational</ENT>
                            <ENT>8,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Alien ownership violation</ENT>
                            <ENT>8,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Failure to permit inspection</ENT>
                            <ENT>7,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Transmission of indecent/obscene materials</ENT>
                            <ENT>7,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Interference</ENT>
                            <ENT>7,000</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="42635"/>
                            <ENT I="01">Importation or marketing of unauthorized equipment</ENT>
                            <ENT>7,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Exceeding of authorized antenna height</ENT>
                            <ENT>5,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Fraud by wire, radio or television</ENT>
                            <ENT>5,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unauthorized discontinuance of service</ENT>
                            <ENT>5,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Use of unauthorized equipment</ENT>
                            <ENT>5,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Exceeding power limits</ENT>
                            <ENT>4,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Failure to Respond to Commission communications</ENT>
                            <ENT>4,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Violation of sponsorship ID requirements</ENT>
                            <ENT>4,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unauthorized emissions</ENT>
                            <ENT>4,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Using unauthorized frequency</ENT>
                            <ENT>4,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Failure to engage in required frequency coordination</ENT>
                            <ENT>4,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Construction or operation at unauthorized location</ENT>
                            <ENT>4,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Violation of requirements pertaining to broadcasting of lotteries or contests</ENT>
                            <ENT>4,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Violation of transmitter control and metering requirements</ENT>
                            <ENT>3,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Failure to file required forms or information</ENT>
                            <ENT>3,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Failure to implement the STIR/SHAKEN authentication framework (continuing violation until cured)</ENT>
                            <ENT>2,500</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Per call know your upstream provider violations</ENT>
                            <ENT>2,500</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Per call violations of the robocall blocking rules</ENT>
                            <ENT>2,500</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Failure to make required measurements or conduct required monitoring</ENT>
                            <ENT>2,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Failure to provide station ID</ENT>
                            <ENT>1,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Unauthorized pro forma transfer of control</ENT>
                            <ENT>1,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Failure to maintain required records</ENT>
                            <ENT>1,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Failure to update Robocall Mitigation Database within 10 business days (continuing violation until cured)</ENT>
                            <ENT>1,000</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Per call caller ID authentication attestation violations</ENT>
                            <ENT>1,000</ENT>
                        </ROW>
                    </GPOTABLE>
                    <STARS/>
                    <PART>
                        <HD SOURCE="HED">PART 64—MISCELLANEOUS RULES RELATING TO COMMON CARRIERS</HD>
                    </PART>
                    <AMDPAR>3. The authority citation for part 64 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 47 U.S.C. 151, 152, 154, 201, 202, 217, 218, 220, 222, 225, 226, 227, 227b, 228, 251(a), 251(e), 254(k), 255, 262, 276, 403(b)(2)(B), (c), 616, 620, 716, 1401-1473, unless otherwise noted; Pub. L. 115-141, Div. P, sec. 503, 132 Stat. 348, 1091; Pub. L. 117-338, 136 Stat. 6156.</P>
                    </AUTH>
                    <AMDPAR>4. Amend § 64.1200 by revising paragraph (n)(5) and adding paragraph (n)(6) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 64.1200 </SECTNO>
                        <SUBJECT>Delivery restrictions.</SUBJECT>
                        <STARS/>
                        <P>(n) A voice service provider must:</P>
                        <P>(5) Take affirmative, effective measures to prevent any voice service provider directly upstream from it, foreign or domestic, from using its network or services to transmit illegal calls, including knowing its upstream voice service provider. For purposes of this rule, a voice service provider must:</P>
                        <P>(i) Collect directly from the upstream provider general business information, financial information, internet commercial presence information, ownership and affiliate information, operational information, and service information or an explanation for why the upstream provider cannot produce any such information;</P>
                        <P>(ii) perform due diligence of the upstream provider's compliance with Commission rules related to the provision of service;</P>
                        <P>(iii) perform due diligence to verify the validity and authenticity of the upstream provider, the information the provider obtained from or about the upstream provider, and the upstream provider's explanation for any information it could not produce, including:</P>
                        <P>(a) Confirming any phone numbers and email addresses are active;</P>
                        <P>(b) Participating in a verbal communication with one or more human principals, owners, or company leaders;</P>
                        <P>(c) Conducting general research to identify risk factors or contradictory information;</P>
                        <P>(d) Reviewing the upstream provider's internet commercial presence information to identify risk factors or contradictory information;</P>
                        <P>(e) Conducting a basic comparative analysis of the information to identify inconsistencies among the information and consistencies with information concerning other upstream providers; and</P>
                        <P>(f) Evaluating the upstream provider's financial information to identify risk factors;</P>
                        <P>(iv) Monitor the upstream provider by:</P>
                        <P>(a) Regularly checking the upstream provider's compliance with Commission rules related to the provision of service;</P>
                        <P>(b) Using call analytics on an ongoing basis to identify illegal or suspect calls or call patterns from the upstream provider,</P>
                        <P>(c) Evaluate on a timely basis information or evidence it finds, receives, or is made aware of that the upstream provider is transmitting illegal calls, failing to authenticate calls, or authenticating calls with improper attestations;</P>
                        <P>(d) evaluating on a timely basis whether any information or evidence it finds, receives, or is made aware presents inconsistencies with other information obtained from or about the upstream provider under this paragraph (n)(5); and</P>
                        <P>(e) Evaluating on a timely basis any other new information or evidence it finds, receives, or is made aware of concerning the upstream provider's reputation.</P>
                        <P>(v) Perform a holistic, totality of the circumstances evaluation of the upstream provider based on the actions taken under this paragraph (n)(5) and implement measures to refuse or discontinue service:</P>
                        <P>(a) When the results do not form an objectively reasonable basis for concluding that the upstream provider is a valid and authentic entity;</P>
                        <P>(b) When the results form an objectively reasonable basis for concluding that the upstream provider is likely to use or is using its network or services to transmit illegal calls or enable the transmission of illegal calls;</P>
                        <P>
                            (c) When the upstream provider does not have a filing in the RMD, does not have an SPC token, is on the Foreign 
                            <PRTPAGE P="42636"/>
                            Adversary Control System or the Covered List, has had a Commission license revoked, or has been the subject of any other Commission enforcement actions that deny its ability to provision voice service; or
                        </P>
                        <P>(d) When the provider finds, receives, or is made aware that the upstream provider does not have mechanisms in place to ensure its customers, upstream providers, clients, employees, and contractors comply with federal and state laws and regulations concerning unlawful calls, including requirements in paragraph (n)(4) of this section or in this paragraph (n)(5);</P>
                        <P>(vi) Retain the information it collects for the upstream provider for a period of four (4) years; and</P>
                        <P>(vii) Report to the Commission's Enforcement Bureau and the Governance Authority any voice service provider it reasonably believes is or may be transmitting illegal calls or violating this paragraph (n)(5).</P>
                        <P>(6) Block any SIP call it receives from another voice service provider that uses North American Numbering Plan resources in the caller identification field and does not have authenticated caller identification information in accordance with § 64.6301, except that it must:</P>
                        <P>(i) Not block a SIP call if the call is placed to 911 or the 988 Suicide and Crisis Lifeline; and</P>
                        <P>(ii) Make all reasonable efforts to ensure that it does not block any call from a public safety answering point or government emergency number.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>5. Revise § 64.6300 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 64.6300 </SECTNO>
                        <SUBJECT>Definitions.</SUBJECT>
                        <P>
                            <E T="03">Authenticate caller identification information.</E>
                             The term “authenticate caller identification information” refers to the process by which a voice service provider attests to the accuracy of caller identification information transmitted with a call.
                        </P>
                        <P>
                            <E T="03">Caller identification information.</E>
                             The term “caller identification information” has the same meaning given the term “caller identification information” in § 64.1600(c) as it currently exists or may hereafter be amended.
                        </P>
                        <P>
                            <E T="03">Certificate.</E>
                             The term “certificate” refers to a digital data object obtained from a Certification Authority which is used by a voice service provider to sign and verify caller identification information consistent with the STIR/SHAKEN authentication framework.
                        </P>
                        <P>
                            <E T="03">Certification Authority.</E>
                             The term “Certification Authority” refers to an entity that issues certificates and vouches for the binding between the data items in a certificate.
                        </P>
                        <P>
                            <E T="03">Customer.</E>
                             The term “customer” refers to any individual or entity that purchases voice service from a voice service provider.
                        </P>
                        <P>
                            <E T="03">Domestic voice service provider.</E>
                             The term “domestic voice service provider” refers to a voice service provider that is not a foreign voice service provider.
                        </P>
                        <P>
                            <E T="03">Downstream.</E>
                             The term “downstream” refers to a point closer to the destination of a call.
                        </P>
                        <P>
                            <E T="03">End User.</E>
                             The term “end user” refers to the ultimate consumer of voice service.
                        </P>
                        <P>
                            <E T="03">Foreign voice service provider.</E>
                             The term “foreign voice service provider” refers to a voice service provider that was created, incorporated, or organized outside of the United States, regardless of whether it has an office, operation, or facilities in the United States.
                        </P>
                        <P>
                            <E T="03">Gateway provider.</E>
                             The term “gateway provider” means a domestic voice service provider that is an intermediate provider that accepts voice calls directly from a foreign voice service provider before transmitting the call downstream to another domestic voice service provider.
                        </P>
                        <P>
                            <E T="03">Governance Authority.</E>
                             The term “Governance Authority” refers to the Secure Telephone Identity Governance Authority, which is the entity that establishes and governs the policies regarding the issuance, management, and revocation of Service Provider Code (SPC) tokens to voice service providers.
                        </P>
                        <P>
                            <E T="03">Improper attestation.</E>
                             The term “improper attestation” means any attestation level that does not conform with ATIS-1000074 and § 64.6301, including any attestation that is inconsistent with the information the voice service provider has, or is required to have, about a call.
                        </P>
                        <P>
                            <E T="03">Industry traceback consortium.</E>
                             The term “industry traceback consortium” refers to the consortium that conducts private-led efforts to trace back the origin of suspected unlawful robocalls as selected by the Commission pursuant to § 64.1203.
                        </P>
                        <P>
                            <E T="03">Initiation.</E>
                             The term “initiation” refers to the action performed by a voice service customer in commencing a call, and does not include origination.
                        </P>
                        <P>
                            <E T="03">Initiating provider.</E>
                             The term “initiating provider” refers to a voice service provider that performs initiation.
                        </P>
                        <P>
                            <E T="03">Intermediate provider.</E>
                             The term “intermediate provider” means a voice service provider that carries or processes calls but neither performs the origination or termination of those calls.
                        </P>
                        <P>
                            <E T="03">Non-gateway intermediate provider.</E>
                             The term “non-gateway intermediate provider” means a voice service provider that is an intermediate provider but is not a gateway provider.
                        </P>
                        <P>
                            <E T="03">Originating provider.</E>
                             The term “originating provider” refers to a voice service provider that performs the origination of a given call.
                        </P>
                        <P>
                            <E T="03">Origination.</E>
                             The term “origination” refers to the technological act of placing a customer's outgoing call onto the network using the provider's own facilities.
                        </P>
                        <P>
                            <E T="03">Policy Administrator.</E>
                             The term “Policy Administrator” refers to a STIR/SHAKEN governance body that applies rules set by the Governance Authority, confirms that Certification Authorities are authorized to issue certificates, and confirms that voice service providers are authorized to request and receive certificates.
                        </P>
                        <P>
                            <E T="03">Robocall Mitigation Database.</E>
                             The term “Robocall Mitigation Database” refers to a database accessible via the Commission's website that lists all entities that make filings pursuant to § 64.6305(b).
                        </P>
                        <P>
                            <E T="03">SIP call.</E>
                             The term “SIP call” refers to a call that is initiated, originated, carried, processed, and terminated using the Session Initiation Protocol signaling protocol.
                        </P>
                        <P>
                            <E T="03">SPC token.</E>
                             The term “SPC token” refers to the Service Provider Code token, which is an authority token validly issued to a voice service provider that allows the provider to obtain a certificate from a Certification Authority.
                        </P>
                        <P>
                            <E T="03">STIR/SHAKEN authentication framework.</E>
                             The term “STIR/SHAKEN authentication framework” means the Secure Telephone Identity Revisited and Signature-based Handling of Asserted information using toKENs standards.
                        </P>
                        <P>
                            <E T="03">Terminating provider.</E>
                             The term “terminating provider” refers to a voice service provider that performs the termination of a given call.
                        </P>
                        <P>
                            <E T="03">Termination.</E>
                             The term “termination” refers to the technological act of serving to a customer an incoming call received on a provider's own facilities that are interconnected with the public network.
                        </P>
                        <P>
                            <E T="03">Upstream.</E>
                             The term “upstream” refers to a point closer to the source of a call.
                        </P>
                        <P>
                            <E T="03">Verify caller identification information.</E>
                             The term “verify caller identification information” refers to the process by which a terminating provider confirms that the caller identification information transmitted with a call for which it performs termination was properly authenticated.
                        </P>
                        <P>
                            <E T="03">Voice service.</E>
                             The term “voice service”—
                        </P>
                        <P>
                            (1) Means any service that is interconnected with the public switched 
                            <PRTPAGE P="42637"/>
                            telephone network and that furnishes voice communications to an end user using resources from the North American Numbering Plan or any successor to the North American Numbering Plan adopted by the Commission under Section 251(e)(1) of the Communications Act of 1934, as amended; and
                        </P>
                        <P>(2) Includes—</P>
                        <P>(i) Transmissions from a telephone facsimile machine, computer, or other device to a telephone facsimile machine; and</P>
                        <P>(ii) Without limitation, any service that enables real-time, two-way voice communications, including any service that requires internet Protocol-compatible customer premises equipment and permits out-bound calling, whether or not the service is one-way or two-way Voice over internet Protocol.</P>
                        <P>
                            <E T="03">Voice service provider.</E>
                             The term “voice service provider” means any entity that provides voice service for a given call.
                        </P>
                    </SECTION>
                    <AMDPAR>6. Revise § 64.6301 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 64.6301 </SECTNO>
                        <SUBJECT>Caller ID authentication in IP networks.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">STIR/SHAKEN implementation.</E>
                             Except as provided in § 64.6301(f), each voice service provider shall fully implement the STIR/SHAKEN authentication framework in its internet Protocol networks in accordance with the STIR/SHAKEN authentication framework standards and this § 64.6301. To fulfill this obligation:
                        </P>
                        <P>(1) An originating or intermediate provider shall:</P>
                        <P>(i) obtain an SPC token from the Secure Telephone Identity Policy Administrator in accordance with the Governance Authority token access policy; and</P>
                        <P>(ii) use that SPC token to obtain Secure Telephone Identity certificates from a Secure Telephone Identity Certification Authority in accordance with the Governance Authority certificate policy;</P>
                        <P>(2) An originating provider shall, using the certificates obtained pursuant to paragraph (a)(1)(ii) of this section, authenticate caller identification information consistent with the attestation-level decisions made pursuant to § 64.6301(d) for all SIP calls for which it performs origination that will exclusively transit its own network or that it will exchange with another voice service provider;</P>
                        <P>(3) A non-gateway intermediate provider shall, using the certificates obtained pursuant to paragraph (a)(1)(ii) of this section, authenticate caller identification information for all calls it receives from a domestic voice service provider that use North American Numbering Plan resources in the caller identification field and that are not SIP calls and which it will exchange with another provider as a SIP call;</P>
                        <P>(4) A gateway provider shall, using the certificates obtained pursuant to paragraph (a)(1)(ii) of this section, authenticate caller identification information for all calls it receives from a foreign voice service provider that use North American Numbering Plan resources in the caller identification field for which the caller identification information has not been authenticated and which it will exchange with another provider as a SIP call; and</P>
                        <P>(5) An intermediate provider shall pass unaltered to the next voice service provider in the call path any authenticated caller identification information it receives with a SIP call, except:</P>
                        <P>(i) where necessary for technical reasons to complete the call; or</P>
                        <P>(ii) where the intermediate provider reasonably believes the caller identification authentication information presents an imminent threat to its network security; so long as</P>
                        <P>(iii) it re-authenticates caller identification information using the certificates obtained pursuant to paragraph (a)(1)(ii) of this section; and</P>
                        <P>(6) A terminating provider shall verify authenticated caller identification information for all SIP calls for which it performs termination that exclusively transit its own network or that it receives from another voice service provider.</P>
                        <P>
                            (b) 
                            <E T="03">Attestation requirements and prohibitions.</E>
                             A voice service provider shall not willfully apply attestation levels inconsistent with the following criteria for each level:
                        </P>
                        <P>
                            (1) 
                            <E T="03">A-level attestations.</E>
                             To authenticate the caller identification information of a call with an A-level attestation, a voice service provider shall, consistent with the STIR/SHAKEN authentication framework:
                        </P>
                        <P>(i) be responsible for the origination of the call onto the IP network,</P>
                        <P>(ii) have a direct, authenticated relationship with the customer associated with the call and be able to identify the customer by satisfying the requirements in § 64.1200(n)(4)-(5), and</P>
                        <P>(iii) establish a verified association between the customer and the telephone number used for a call, which shall presumptively be satisfied if the provider assigned the telephone number to the customer and shall not be satisfied by a business agreement or certification that includes a general statement that the customer will only use numbers with which it has a verified association or when the numbers meet the conditions in § 64.1200(o).</P>
                        <P>
                            (2) 
                            <E T="03">B-level attestations.</E>
                             To authenticate the caller identification information of a call with a B-level attestation, a voice service provider shall, consistent with the STIR/SHAKEN authentication framework:
                        </P>
                        <P>(i) be responsible for the origination of the call onto the IP network,</P>
                        <P>(ii) have a direct, authenticated relationship with the customer associated with the call and be able to identify the customer by satisfying the requirements in § 64.1200(n)(4)-(5), and</P>
                        <P>(iii) be unable to establish a verified association between the customer and the telephone number used for a call.</P>
                        <P>
                            (3) 
                            <E T="03">C-level attestations.</E>
                             To authenticate the caller identification information of a call with a C-level attestation, a voice service provider shall, consistent with the STIR/SHAKEN authentication framework:
                        </P>
                        <P>(i) not be responsible for the origination of a call onto the IP network, or</P>
                        <P>(ii) not have a direct, authenticated relationship with the customer associated with the call or be able to identify the customer.</P>
                        <P>
                            (c) 
                            <E T="03">Third-party authentication.</E>
                             An originating or intermediate provider may fulfill its obligations to authenticate caller identification information under paragraphs (a)(2)-(3) of this section by entering into an agreement with a third-party authentication service, provided that the provider:
                        </P>
                        <P>(1) requires the third party to sign all calls using the certificate obtained by the provider in accordance with paragraph (a)(1)(ii) of this section;</P>
                        <P>(2) makes all attestation-level decisions regarding the caller identification information of each call in accordance with paragraph (b);</P>
                        <P>(3) memorializes the agreement between it and the third party for the authentication service in writing, which must:</P>
                        <P>(i) specify the tasks that the third-party authentication service will perform on the provider's behalf, and</P>
                        <P>(ii) confirm that the provider shall make all attestation-level decisions for calls signed pursuant to the agreement, and that all calls shall be signed using the provider's Secure Telephone Identity certificate;</P>
                        <P>(4) maintains any agreement entered into pursuant to paragraph (d)(3) of this section for as long as any third-party authentication arrangement exists; and</P>
                        <P>
                            (5) retains a copy of any agreement entered into pursuant to paragraph (d)(3) of this section for a period of two 
                            <PRTPAGE P="42638"/>
                            (2) years from the end or termination of the agreement.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Attestation requirements for voice service providers serving end users directly.</E>
                             A voice service provider that serves end users directly shall make all attestation-level decisions regarding the caller identification information of each of its end users' SIP calls consistent with paragraph (b) of this section, regardless of whether it has a STIR/SHAKEN implementation obligation.
                        </P>
                        <P>
                            (e) 
                            <E T="03">Prohibition on elective non-IP routing.</E>
                             A voice service provider shall not intentionally cause a call to be routed over a network that does not support the transmission of authenticated caller identification information when it has the technical ability to cause the call to be routed over a network that does support the transmission of authenticated caller identification information.
                        </P>
                        <P>
                            (f) 
                            <E T="03">Implementation extensions and exemptions.</E>
                        </P>
                        <P>
                            (1) 
                            <E T="03">Annual review of undue hardship extensions.</E>
                             The Wireline Competition Bureau shall, in conjunction with an assessment of burdens and barriers to implementation of caller identification authentication technology, annually review the scope of all previously granted undue hardship extensions and, after issuing a Public Notice seeking comment, may extend or decline to extend each such extension, and may decrease the scope of entities subject to a further extension.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Non-IP networks extension.</E>
                             Those portions of a voice service provider's network that rely on technology that cannot initiate, maintain, carry, process, and terminate SIP calls are deemed subject to a continuing extension. A voice service provider subject to the foregoing extension shall comply with the requirements of § 64.6303(a) as to the portion of its network subject to the extension.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Non-facilities-based provider exemption.</E>
                             A voice service provider is exempt from implementing the STIR/SHAKEN authentication framework as described in paragraph (a) of this section to the extent that it is a non-facilities-based provider for a given call.
                        </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 64.6302 </SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>7. Remove and reserve § 64.6302.</AMDPAR>
                    <AMDPAR>8. Revise § 64.6303 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 64.6303 </SECTNO>
                        <SUBJECT>Caller ID authentication in non-IP networks.</SUBJECT>
                        <P>(a) A voice service provider shall either:</P>
                        <P>(1) Upgrade its entire network to allow for the origination, carrying, processing, and termination, as applicable, of SIP calls and fully implement the STIR/SHAKEN authentication framework as required in § 64.6301 throughout its network; or</P>
                        <P>(2) Maintain and be ready to provide the Commission upon request with documented proof that it is participating, either on its own or through a representative, including third party representatives, as a member of a working group, industry standards group, or consortium that is working to develop a non-internet Protocol caller identification authentication solution, or actively testing such a solution.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 64.6304 </SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>9. Remove and reserve § 64.6304.</AMDPAR>
                    <AMDPAR>10. Revise § 64.6305 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 64.6305 </SECTNO>
                        <SUBJECT>Robocall mitigation and certification.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Robocall mitigation program requirements.</E>
                             Each voice service provider shall implement an appropriate robocall mitigation program that shall include:
                        </P>
                        <P>(1) reasonable steps to prevent its network or services from being used to transmit illegal robocalls; and</P>
                        <P>(2) a commitment:</P>
                        <P>(i) to respond fully and within 24 hours to all traceback requests from the Commission, law enforcement, and the industry traceback consortium; and</P>
                        <P>(ii) to cooperate with such entities in investigating and stopping any person or entity from using the voice service provider's network or services to transmit illegal robocalls.</P>
                        <P>
                            (b) 
                            <E T="03">Certification in the Robocall Mitigation Database.</E>
                        </P>
                        <P>(1) A voice service provider shall certify that all of the calls its network or services transmit are subject to a robocall mitigation program consistent with paragraph (a) of this section, that any prior certification has not been removed by Commission action, and that it has not been prohibited from filing in the Robocall Mitigation Database by the Commission.</P>
                        <P>(2) A facilities-based voice service provider shall certify to one of the following:</P>
                        <P>(i) It has fully implemented the STIR/SHAKEN authentication framework across its entire network and services and all calls it transmits are compliant with § 64.6301;</P>
                        <P>(ii) It has implemented the STIR/SHAKEN authentication framework on a portion of its network and services and all calls it transmits on that portion of its network are compliant with § 64.6301; or</P>
                        <P>(iii) It has not implemented the STIR/SHAKEN authentication framework on any portion of its network.</P>
                        <P>(3) A voice service provider that serves end users directly shall certify that it is compliant with the attestation requirements in § 64.6301(b) for all calls it transmits on its services.</P>
                        <P>(4) A voice service provider shall include the following information in its certification in English or with a certified English translation:</P>
                        <P>(i) If it is has certified that it has not implemented the STIR/SHAKEN authentication framework on any portion of its network pursuant to paragraphs (b)(2)(ii) or (b)(2)(iii) of this section, identification of the exemption(s) or extension(s) the voice service provider received under § 64.6301(f) for that portion of the network, if the voice service provider is not a foreign voice service provider, and the basis for the exemption(s) or extension(s);</P>
                        <P>(ii) The specific reasonable steps the voice service provider has taken to prevent its network or services from being used to transmit illegal robocalls as part of its robocall mitigation program, including a description of how it complies with its obligation to know its customers and/or know its upstream providers, as applicable, pursuant to § 64.1200(n)(4)-(5), the analytics system(s) it uses to identify and block illegal calls, including whether it uses any third-party analytics vendor(s) and the name(s) of such vendor(s);</P>
                        <P>(iii) A statement of the voice service provider's commitment to respond fully and within 24 hours to all traceback requests from the Commission, law enforcement, and the industry traceback consortium, and to cooperate with such entities in investigating and stopping any illegal robocallers that use its network or services to transmit illegal robocalls; and</P>
                        <P>
                            (iv) State whether, at any time in the prior two years, the filing entity (and/or any entity for which the filing entity shares common ownership, management, directors, or control) has been the subject of a formal Commission, law enforcement, or regulatory agency action or investigation with accompanying findings of actual or suspected wrongdoing due to the filing entity transmitting, encouraging, assisting, or otherwise facilitating illegal robocalls or spoofing, or a deficient Robocall Mitigation Database certification or mitigation program description; and, if so, provide a description of any such action or investigation, including all law enforcement or regulatory agencies involved, the date that any action or investigation was commenced, the current status of the action or investigation, a summary of the findings 
                            <PRTPAGE P="42639"/>
                            of wrongdoing made in connection with the action or investigation, and whether any final determinations have been issued.
                        </P>
                        <P>(6) A voice service provider filing a certification pursuant to paragraph (b) of this section shall submit the following information in the Robocall Mitigation Database:</P>
                        <P>(i) The voice service provider's business name(s) and primary address;</P>
                        <P>(ii) Other business names in use by the voice service provider;</P>
                        <P>(iii) All business names previously used by the voice service provider;</P>
                        <P>(iv) Whether the voice service provider is a foreign voice service provider;</P>
                        <P>(v) The name, title, department, business address, telephone number, and email address of one person within the company responsible for addressing robocall mitigation-related issues;</P>
                        <P>(vi) Whether or not the voice service provider has a STIR/SHAKEN authentication framework implementation obligation;</P>
                        <P>(vii) Whether the voice service provider:</P>
                        <P>(A) Is a facilities-based provider that:</P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) Is an originating or terminating voice service provider directly serving end users;
                        </P>
                        <P>
                            (
                            <E T="03">2</E>
                            ) Is an originating or terminating provider acting as a wholesale provider originating or terminating calls on behalf of another provider or providers;
                        </P>
                        <P>
                            (
                            <E T="03">3</E>
                            ) Is a gateway provider; and/or
                        </P>
                        <P>
                            (
                            <E T="03">4</E>
                            ) Is a non-gateway intermediate provider; or
                        </P>
                        <P>(B) Is a non-facilities-based provider; and/or</P>
                        <P>(viii) The voice service provider's OCN, if it has one.</P>
                        <P>(5) All certifications made and information submitted pursuant to paragraph (b) of this section shall:</P>
                        <P>(i) Be filed in the Robocall Mitigation Database; and</P>
                        <P>(ii) Be signed by an officer in conformity with § 1.16.</P>
                        <P>(7) A voice service provider shall update its filings within ten (10) business days of any change to the information it must provide pursuant to paragraph (b) of this section.</P>
                        <P>(i) A voice service provider that has been aggrieved by a Governance Authority decision to revoke that voice service provider's SPC token need not update its filing on the basis of that revocation until the sixty (60)-day period to request Commission review pursuant to § 64.6308(b)(1), following completion of the Governance Authority's formal review process, expires or, if the aggrieved voice service provider files an appeal, until ten (10) business days after the Wireline Competition Bureau releases a final decision pursuant to § 64.6308(d)(1).</P>
                        <P>(ii) If a voice service provider elects not to file a formal appeal of the Governance Authority decision to revoke that voice service provider's SPC token, the provider need not update its filing on the basis of that revocation until the thirty (30) day period to file a formal appeal with the Governance Authority Board expires.</P>
                        <P>
                            (c) 
                            <E T="03">Intermediate and terminating voice service provider obligations</E>
                            —
                        </P>
                        <P>
                            (1) 
                            <E T="03">Accepting calls from domestic voice service providers.</E>
                             Intermediate and terminating providers shall accept calls directly from a domestic voice service provider only if that domestic voice service provider's filing appears in the Robocall Mitigation Database in accordance with paragraph (b) of this section, showing that the voice service provider has affirmatively submitted the filing, and that filing has not been de-listed pursuant to an enforcement action.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Accepting calls from foreign voice service providers.</E>
                             Intermediate and terminating providers shall accept calls directly from a foreign voice service provider that uses North American Numbering Plan resources in the caller identification field to send voice calls to residential or business subscribers in the United States, only if that foreign voice service provider's filing appears in the Robocall Mitigation Database in accordance with paragraph (b) of this section, showing that the foreign voice service provider has affirmatively submitted the filing, and that filing has not been de-listed pursuant to an enforcement action.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Public safety safeguards.</E>
                             Notwithstanding paragraph (c)(1) and (2):
                        </P>
                        <P>(i) A provider may not block a voice call under any circumstances if the call is an emergency call placed to 911; and</P>
                        <P>(ii) A provider must make all reasonable efforts to ensure that it does not block any calls from public safety answering points and government emergency numbers.</P>
                        <P>
                            (d) 
                            <E T="03">Annual Recertification Requirement.</E>
                             In accordance with this section and § 1.16, all providers shall certify annually, on or before March 1, that any information submitted to the Robocall Mitigation Database is true and correct.
                        </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 64.6306 </SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>11. Remove and reserve § 64.6306.</AMDPAR>
                    <AMDPAR>12. Revise § 64.6307 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 64.6307 </SECTNO>
                        <SUBJECT>Line item charges.</SUBJECT>
                        <P>(a) Voice service providers are prohibited from adding any additional line item charges to consumer subscribers or small business customer subscribers for the effective caller identification authentication technology required by § 64.6301 and § 64.6303.</P>
                        <P>(1) For purposes of this section, “consumer subscribers” means residential mass-market subscribers.</P>
                        <P>(2) For purposes of this section, “small business customer subscribers” means subscribers that are business entities that meet the size standards established in 13 CFR part 121, subpart A.</P>
                    </SECTION>
                    <AMDPAR>13. Revise § 64.6308 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 64.6308 </SECTNO>
                        <SUBJECT>Review of Governance Authority Decision to Revoke an SPC Token.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Parties permitted to seek review of Governance Authority decision.</E>
                        </P>
                        <P>(1) Any voice service provider aggrieved by a Governance Authority decision to revoke that voice service provider's SPC token, must seek review from the Governance Authority and complete the appeals process established by the Governance Authority prior to seeking Commission review.</P>
                        <P>(2) Any voice service provider aggrieved by an action to revoke its SPC token taken by the Governance Authority, after exhausting the appeals process provided by the Governance Authority, may then seek review from the Commission, as set forth in this section.</P>
                        <P>
                            (b) 
                            <E T="03">Filing deadlines.</E>
                        </P>
                        <P>(1) A voice service provider requesting Commission review of a Governance Authority decision to revoke that voice service provider's SPC token by the Commission, shall file such a request electronically in the Electronic Comment Filing System (ECFS) in WC Docket No. 21-291, Appeals of the STIR/SHAKEN Governance Authority Token Revocation Decisions within sixty (60) days from the date the Governance Authority upholds it token revocation decision.</P>
                        <P>(2) Parties shall adhere to the time periods for filing oppositions and replies set forth in § 1.45.</P>
                        <P>
                            (c) 
                            <E T="03">Filing requirements.</E>
                        </P>
                        <P>
                            (1) A request for review of a Governance Authority decision to revoke a voice service provider's SPC token by the Commission shall be filed in WC Docket No. 21-291, Appeals of the STIR/SHAKEN Governance Authority Token Revocation Decisions, in the Electronic Comment Filing System (ECFS). The request for review shall be captioned “In the matter of Request for Review by (name of party seeking review) of Decision of the 
                            <PRTPAGE P="42640"/>
                            Governance Authority to Revoke an SPC Token.”
                        </P>
                        <P>(2) A request for review shall contain:</P>
                        <P>(i) A statement setting forth the voice service provider's asserted basis for appealing the Governance Authority's decision to revoke the SPC token;</P>
                        <P>(ii) A full statement of relevant, material facts with supporting affidavits and documentation, including any background information the voice service provider deems useful to the Commission's review; and</P>
                        <P>(iii) The question presented for review, with reference, where appropriate, to any underlying Commission rule or Governance Authority policy.</P>
                        <P>
                            (3) A copy of a request for review that is submitted to the Commission shall be served on the Governance Authority by the voice service provider requesting Commission review via 
                            <E T="03">sti-ga@atis.org</E>
                             or in accordance with any alternative delivery mechanism the Governance Authority may establish in its operating procedures.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Review by the Wireline Competition Bureau.</E>
                        </P>
                        <P>(1) Except in extraordinary circumstances, final action on a request for review of a Governance Authority decision to revoke a voice service provider's SPC token should be expected no later than one hundred and eighty (180) days from the date the request for review is filed in the Electronic Comment Filing System (ECFS) pursuant to § 64.6308(b)(1). The Wireline Competition Bureau shall have the discretion to pause the one hundred and eighty (180)-day review period in situations where actions outside the Wireline Competition Bureau's control are responsible for delaying review of a request for review.</P>
                        <P>(2) An affected party may seek review of a decision issued under delegated authority by the Wireline Competition Bureau pursuant to the rules set forth in § 1.115.</P>
                        <P>
                            (e) 
                            <E T="03">Standard of review.</E>
                             The Wireline Competition Bureau shall conduct 
                            <E T="03">de novo</E>
                             review of Governance Authority decisions to revoke a voice service provider's SPC token.
                        </P>
                        <P>
                            (f) 
                            <E T="03">Status during pendency of a request for review and a Governance Authority decision.</E>
                        </P>
                        <P>(1) A voice service provider shall not be considered to be in violation of the Commission's caller identification authentication rules under § 64.6301 after revocation of its SPC token by the Governance Authority until the thirty (30) day period to file a formal appeal with the Governance Authority Board expires, or during the pendency of any formal appeal to the Governance Authority Board.</P>
                        <P>(2) A voice service provider shall not be considered to be in violation of the Commission's caller identification authentication rules under § 64.6301 after the Governance Authority Board upholds the Governance Authority's SPC token revocation decision until the sixty (60) day period to file a request for review with the Commission expires.</P>
                        <P>(3) When a voice service provider has sought timely Commission review of a Governance Authority decision to revoke a voice service provider's SPC token under this section, the voice service provider shall not be considered to be in violation of the Commission's caller identification authentication rules under § 64.6301 until and unless the Wireline Competition Bureau, pursuant to paragraph (d)(1) of this section, has upheld or otherwise decided not to overturn the Governance Authority's decision.</P>
                        <P>(4) In accordance with §§ 1.102(b) and 1.106(n), the effective date of any action pursuant to paragraph (d) of this section shall not be stayed absent order by the Wireline Competition Bureau or the Commission.</P>
                    </SECTION>
                    <AMDPAR>14. Add § 64.6309 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 64.6309 </SECTNO>
                        <SUBJECT>Governance Authority Policies</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">SPC Token Issuance and Revocations Policies.</E>
                        </P>
                        <P>(1) The Governance Authority shall adopt a policy that includes affirmative, effective measures to prevent voice service providers that are issued SPC tokens from transmitting calls that are not in compliance with the STIR/SHAKEN authentication framework, the Commission's STIR/SHAKEN rules, or the Governance Authority's policies, including a policy for the issuance of SPC tokens that follows the requirements in § 64.1200(n)(5)(i)-(iii).</P>
                        <P>(2) The Governance Authority shall adopt a policy to review all information it receives concerning an SPC token holder and its conduct, further investigate the SPC token holder and its conduct when there is a reasonable basis for believing the SPC token holder is not or is unlikely to be in compliance with the STIR/SHAKEN authentication framework, the Commission's STIR/SHAKEN rules, and/or the Governance Authority's policies, and deny or revoke an SPC token when it concludes that the SPC token holder is not in compliance or is not likely to comply with such requirements.</P>
                        <P>
                            (b) 
                            <E T="03">Selection of Secure Telephone Identity Certification Authorities.</E>
                        </P>
                        <P>(1) The Governance Authority shall adopt a policy that includes affirmative, effective measures to prevent Certification Authorities from failing to comply with the STIR/SHAKEN authentication framework, the Commission's STIR/SHAKEN rules, or the Governance Authority's policies, including a policy for the selection of Certification Authorities that follows the requirements in § 64.1200(n)(5)(i) and (ii).</P>
                        <P>(2) The Governance Authority shall adopt a policy to review all information it receives concerning a Certification Authority and its conduct, further investigate the Certification Authority and its conduct when there is a reasonable basis for believing the Certification Authority has violated or may violate the STIR/SHAKEN authentication framework, the Commission's STIR/SHAKEN rules, and/or the Governance Authority's policies, and deny or remove the Certification Authority when it concludes that the Certification Authority is not in compliance or is not likely to comply with such requirements.</P>
                        <P>
                            (c) 
                            <E T="03">Information Collection.</E>
                             The Governance Authority shall establish measures to regularly obtain from the industry traceback consortium and call analytics providers information about SPC token holder and Certification Authority conduct.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Reporting.</E>
                             The Governance Authority shall report to the Commission on no less than a quarterly basis information about its enforcement activity, including complaints it has received, investigations it has initiated and concluded, and decisions concerning SPC token revocations and Certification Authority removals, including any reports documenting the Governance Authority's final determinations.
                        </P>
                    </SECTION>
                </SUPLINF>
                <FRDOC>[FR Doc. 2026-13874 Filed 7-8-26; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 6712-01-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
</FEDREG>
